So, this question was asked several weeks ago, and, so far, we have no
statistics. I wonder if, now that there appears to be some interest
around GSoC 2017 starting up, someone could look back at their notes and
answer some of these questions.

While it's cool that folks are spending time on GSoC, for the sake of
GSoC, and of the students, it would also be awesome to know whether the
time and money that the ASF puts into this is actually doing something
towards the stated goal of Community Development.

Or, at the very least, can we make a commitment to track this data going
forward?

--Rich

On 11/16/2016 05:18 AM, Nick Burch wrote:
> On Wed, 16 Nov 2016, 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?
> 
> Do we have a list (maybe somewhere in the comdev private svn?) of
> everyone who has taken part in GSoC?
> 
> If so, it'd be fairly easy to annotate that with apache IDs, then see
> who's now on PMCs or who's now a member. Producing sharable statistics
> from that automatically is then easy. (I say this as someone who helped
> update the similar Travel Assistance Committee / TAC ones on Monday!)
> 
> Not sure if it's easy to find out the "last commit date" for people, to
> check for the "still around" part (eg for people who got committership
> during GSoc, maybe on a branch), but I know where infra are to ask...
> 
> Nick
> 
> PS FWIW, within Tika we've certainly had a few GSoC people stick around!
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 


-- 
Rich Bowen - rbo...@rcbowen.com - @rbowen
http://apachecon.com/ - @apachecon

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to