So, since this thread seems to have been perceived as "justify your existence, you layabouts!" let me rephrase, in the hopes of being a little more constructive. Apologies to any who took my question as an attack or accusation. It was neither.
Do we have a comprehensive list of project/particpant going back to when we started doing GSoC? Or can someone point me to a location where such a list could be assembled after the fact? I propose the following concrete tasks/action items. Folks who don't see the value of doing them are encouraged not to do them. Folks who are looking for a way to contribute to the mission of Community Development can consider doing these tasks. 1) Assemble list of participant/project (privately, if there's a privacy concern here?) across the history of GSoC@Apache 2) Foreach $participant in list, is that participant still active in $project. (Subtask: State your definition of "active".) 3) Foreach $participant in list, determine whether the code that they wrote as the C part of GSoC was in fact accepted into $project. (Subtask: Is it still there?) 4) Present items 2 and 3 above as pretty graphs and charts, showing outcomes of each year, and so on. Include these graphs and charts on http://community.apache.org/gsoc and in whatever materials we send to projects when we encourage them to participate in GSoC. 5) Also offer these statistics back to Google. This is both to help them in their recruitment (assuming it's good news) and also as a proactive part of our own community development effort, to draw in the next generation of GSoC participants, and participants in general. On 11/16/2016 04:41 AM, Rich Bowen wrote: > It would be great to have some kind of statistics on how GSoC helps > projects longer term. Do students stick around? Does the code written > actually get incorporated into releases? Does it in fact contribute to > the mission of Community Development, or is it just a nice summer job > for these students? > > To be clear, I don't question the value of GSoC. What I'm curious about > is whether these people actually end up participating in our > communities. My experience with GSoC outside of Apache has been that the > students don't stick around, and so the enormous time and effort put > into GSoC, while it helps the skills and career of these students, > didn't help the project longer term. > -- Rich Bowen - rbo...@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon
signature.asc
Description: OpenPGP digital signature
