I would like to mentor. Also, I think that even if a student doesn't stay, there are ample benefits in GSOC: - we think more about areas which need improvement. - together with students, we explore various ways of approaching the problems we face. - we gain more visibility for other, potential developers (even outside GSoC). - it's fun.
On Wed, Feb 15, 2012 at 8:36 PM, Mark de Wever <[email protected]> wrote: > Hi, > > At the FOSDEM Google announced that there will be a GSoC [1] again. We > also discussed whether or not to join, but decided it would be better to > discuss on this mailing list. > > Some points we discussed at the FOSDEM were: > * GSoC mentoring and preparation cost a lot of time and that time > especially mentoring is done by core developers, who can not use that > time to hack on Wesnoth. > * The amount of students that stay is rather low. The whole idea of GSoC > is to gain new students and keep them. The disadvantages are: > * The project is abandoned after the summer. > * The mentor suddenly has an extra feature to maintain. > * Getting a new student up to speed takes quite some effort, so it > would have been faster if the mentor did the work him/herself. This > should pay itself back by gaining a new developer. The first > happens, the second too little. (That it takes time and is faster to > do it oneself is expected, just like training a new colleague.) > > So the question is do we want to join? > Who will be available as mentor? > Who will be available as project administrator? > > > [1] http://code.google.com/soc/ > -- > Regards, > Mark de Wever aka Mordante/SkeletonCrew > > _______________________________________________ > Wesnoth-dev mailing list > [email protected] > https://mail.gna.org/listinfo/wesnoth-dev -- Cheers, Iurii Chernyi _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
