Talk:Google Summer of Code/2009

The good
List of things that should stay.


 * Project flexibility. It's really nice you can change the to-do's for your project, to not get stuck with certain problems, and get an optimal result. I completely ditched the original idea of the Semantic Layers extension after some discussion with my mentor, and went for Semantic Maps instead. Half way through, it even got slip into 2 parts. --Jeroen De Dauw 00:12, 20 August 2009 (UTC)


 * The awesome project idea's. This made it really easy to create an initial project plan for me. --Jeroen De Dauw 00:12, 20 August 2009 (UTC)

The bad
List of things that could be improved upon for next years GSoC.

That's my opinion on it anyway --Jeroen De Dauw 00:12, 20 August 2009 (UTC)
 * Community support. Wikimedia has a lot of enthusiastic people that have no problem helping a GSoC student out. A central resource for the students is lacking though. It would be awesome if some sort of MediaWiki GSoC group was created at the start of the program, containing all students and all mentors. This would have the following advantages:
 * Students can share idea's with each other, and share solutions for common 'new dev' problems.
 * Students can get support from people who are familiar with the MediaWiki code, different from their mentor. It's better to have multiple strong contacts with the community, and have more then one person review your plans or code. You also don't get stuck when your mentor becomes temporary unavailable by going on holiday or something similar.
 * If a student has problems with his mentor, he doesn't get cut off.
 * The more contacts a student has, and the more he gets support, the more likely he is to remain active in the community afterwards.
 * Such a group could remain after GSoC ends, and would then form a great resource for new students (and mentors) the following year. It could be used to make the whole process more visible and transparent, and so draw in more mentors and students.
 * It's fun!