* Ben Collins-Sussman <sussman@red-bean.com> [2006-04-15 18:53:57]:
> Last year, SoC was a huge success for the Subversion project: five of
> our eight students completed their projects, and two of them even
> became committers. The students gained some great experience (and
> $4500 each for summer employment), and Subversion got a bunch of new
> features (path-based access control in svnserve
Yay!
> 1) Decide how many students we'd like to mentor.
>
> Last year we mentored 8 students. The web form asks how many
> we'd ideally like to have, and at some point Google will repsond
> and tell us how many internships they're willing to allot us.
Recalling my experience of last year's SoC, mentoring 8 students was
handled quite gracefully by the dev list. Well, only about 5 of those
were active iirc, but things went quite smoothly then.
Therefore, I propose that we up that number a little, if we have a
sufficient number of tasks that can be done. Or at least, that we
don't reduce that number.
> 2) Come up with a list of project ideas for students.
>
> Here's a link to last year's ideas page, which we'll need to
> update:
>
> http://subversion.tigris.org/project_tasks.html
I think this year we should fork off a separate page for the SoC,
during the small time period where students are applying (or
considering it). That way, we can cut down on the number of "I want
to take on the Issue Management task for SoC!", and provide a little
direction on what data an application should include, as well as a
list of projects we don't want tackled during SoC ("But, WHY can't I
do merge tracking/SQL backends/distributed versionning this summer?").
If that makes sense, I'll create summer_of_code.html and start filling
it out.
As far as ideas for stuff to do go, a few of the current tasks should
still go on the list: SASL support for svnserve, Optional/compressed
text base storage, and maybe polishing of bindings
(eg. pythonificating the python bindings, that kind of thing). I'll
add those three for a start, and get thinking on more tasks.
- Dave.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 16 04:42:25 2006