Categories
Posts in this category
- A shiny perl6.org site
- Creating an entry point for newcomers
- Sprixel, a 6 compiler powered by JavaScript
- Another perl6.org iteration
- Blackjack and Perl 6
- Why I commit Crud to the Perl 6 Test Suite
- This Week's Contribution to Perl 6 Week 5: Implement Str.trans
- This Week's Contribution to Perl 6
- This Week's Contribution to Perl 6 Week 8: Implement $*ARGFILES for Rakudo
- This Week's Contribution to Perl 6 Week 6: Improve Book markup
- This Week's Contribution to Perl 6 Week 2: Fix up a test
- This Week's Contribution to Perl 6 Week 9: Implement Hash.pick for Rakudo
- This Week's Contribution to Perl 6 - Lottery Intermission
- This Week's Contribution to Perl 6 Week 3: Write supporting code for the MAIN sub
- This Week's Contribution to Perl 6 Week 1: A website for proto
- This Week's Contribution to Perl 6 Week 4: Implement :samecase for .subst
- This Week's Contribution to Perl 6 Week 7: Implement try.rakudo.org
- What is the "Cool" class in Perl 6?
- Report from the Perl 6 Hackathon in Copenhagen
- Custom operators in Rakudo
- A Perl 6 Date Module
- Defined Behaviour with Undefined Values
- Dissecting the "Starry obfu"
- The case for distributed version control systems
- Perl 6: Failing Softly with Unthrown Exceptions
- The first Perl 6 module on CPAN
- Gabor: Keep going
- Google Summer of Code Mentor Recap
- Building a Huffman Tree With Rakudo
- Immutable Sigils and Context
- Is Perl 6 really Perl?
- List.classify
- Perl 6: Lost in Wonderland
- Lots of momentum in the Perl 6 community
- Monetize Perl 6?
- Musing and the future of feather and the Pugs repository
- Musings on Rakudo's spectest chart
- My first executable from Perl 6
- My first YAPC - YAPC::EU 2010 in Pisa
- Trying to implement new operators - failed
- Programming Languages Are Not Zero Sum
- Notes from the YAPC::EU 2010 Rakudo hackathon
- Let's build an object
- Perl 6 is optimized for fun
- How to get a parse tree for a Perl 6 Program
- Pascal's Triangle in Perl 6
- Perl 6 in 2009
- Perl 6 ticket life cycle
- The Perl Survey and Perl 6
- The Perl 6 Advent Calendar
- Perl 6 Questions on Perlmonks
- Physical modeling with Math::Model and Perl 6
- How to Plot a Segment of a Circle with SVG
- Publicity for Perl 6
- Fixing Rakudo Memory Leaks
- Rakudo architectural overview
- Rakudo Rocks
- Rakudo "star" announced
- My personal "I want a PONIE" wish list for Rakudo Star
- Rakudo's rough edges
- Rats and other pets
- Releasing Rakudo made easy
- Set Phasers to Stun!
- Starry Perl 6 obfu
- Recent Perl 6 Developments August 2008
- The State of Regex Modifiers in Rakudo
- Strings and Buffers
- Subroutines vs. Methods - Differences and Commonalities
- A SVG plotting adventure
- A Syntax Highlighter for Perl 6
- Test Suite Reorganization: How to move tests
- The Happiness of Design Convergence
- Perl 6 Tidings from September and October 2008
- Perl 6 Tidings for November 2008
- Perl 6 Tidings from December 2008
- Perl 6 Tidings from January 2009
- Perl 6 Tidings from February 2009
- Perl 6 Tidings from March 2009
- Perl 6 Tidings from April 2009
- Perl 6 Tidings from May 2009
- Perl 6 Tidings from May 2009 (second iteration)
- Perl 6 Tidings from June 2009
- Perl 6 Tidings from August 2009
- Perl 6 Tidings from October 2009
- Timeline for a syntax change in Perl 6
- Visualizing match trees
- Want to write shiny SVG graphics with Perl 6? Port Scruffy!
- We write a Perl 6 book for you
- When we reach 100% we did something wrong
- Where Rakudo Lives Now
- Why was the Perl 6 Advent Calendar such a Success?
- What you can write in Perl 6 today
- Why you don't need the Y combinator in Perl 6
- You are good enough!
Sun, 31 Aug 2008
Google Summer of Code Mentor Recap
Permanent link
Eric Wilhelm asked the mentors of the Google Summer of Code projects 2008 to share their thoughts on the program and their project, so here is my blah.
I mentored Adrian Kreher's project Flesh Out the Perl 6 Test Suite, and overall I'm very pleased.
After being talked into becoming a mentor by Jerry "particle" Gay I was a a little nervous and not really sure if I was up to the task. So I did what my student would be doing later on: write new tests, review old ones, move them to the "official" part of the test suite, and adapt them so that Rakudo can run them (which basically means selectively disabling tests).
On The perl soc mentor's list I found a few links to guides on how to be a good mentor, which I read and which boil down to "communicate with your student, run his code and give him some feedback".
So we (my student and I) made contact, scheduled regular meetings on IRC, I answered a few questions of his, and thus the project began.
Adrian's work was very good in terms of quality, and after a few minor corrections and nits from my part I made myself mostly superfluous, he worked on his own. I continued to monitor his commits, filled out the mid term and end of term surveys, and thusly passed the project for me.
Assessing the work on the test suite is a bit harder than with other project, because most projects had rather clear goals, whereas in this project the goal was "clean up the test suite as much as possible". It was clear from the beginning that Adrian wouldn't be able to make it through the whole test suite (roughly 900 files, 20k+ tests), so the quantitative goal was to create and mofify 1000 tests, which was met, as far as measurable.
As stated before I am very pleased both with Adrian's work (which actually helped the Rakudo developers a lot), and with the whole infrastructure; there was very little administrative work to do and everybody I dealt with was friendly and helpful.
So if all works well (enough free time, and proposals which fit my abilities) I'll surely offer to mentor again.