Any time there is an event that is geared toward further developing open source software, there is always that really big question of whether to do it or not. Let’s face it, a lot of opportunities exist, and decisions have to be made. That’s the hurdle that Jane Wells and the rest of the WordPress development team tackled a week or so back on the development blog regarding the Google Code-in.
Google Code-In is an event hosted by Google to get kids worldwide between the ages of 13 and 17 to participate in open source communities. The WordPress team, if they choose to be a part, will work as mentors to the kids. Unlike Summer of Code, Code-In runs on a much tighter schedule. Turnover times are in hours instead of months.
Jane’s concerns are:
- The lack of student qualification due to open enrollment and no screening process
- Time zone differences causing delays in response times
- Event takes place over the winter holiday season, Nov 21 – Jan 16
- Task list must be pre-created, possibly requiring all mentors to be available for the entire duration
- Multiple task difficulties covering multiple areas with sparse mentor coverage
- Last year’s mentors, with the exception of one, gave negative feedback for last year’s event for multiple reasons
With those concerns and being in the WordPress 3.3 release cycle, she thinks spreading the team’s time and resources even thinner would be a bad idea. The decision isn’t final as of yet and she is open to other opinions. If you want to read more about her concerns and participate in the discussion, check out the post on the WPDevel site.
What do you think should happen? Participate in Code-In or wait and possibly give it another shot next year?