Git and GSoC 2013

There was a big thread about a month ago on whether Git should do Google
Summer of Code this year[1].

Some people seemed in favor, and some not. The deadline for git to apply
to GSoC is March 29 (this Friday) at 19:00 UTC. I am willing to act as
the admin again if list consensus is that we should do it. But my point
in sending this email is not to say "yes, we should definitely apply";
it is to give people on both sides one more chance to make their points
and come to a conclusion before the deadline. I.e., I did not want the
decision to be made for us because people were not aware of the
deadline.

In my opinion, a lot of the issues come down to project selection; one
thing that seemed to come up in the thread was that projects are often
not scoped appropriately to get fully merged by the end of the summer. I
think the much smaller projects done by Matthieu Moy's summer students
in past years have been very successful _because_ they are of a size
much closer to patch series done by normal contributors. I realize that
the GSoC time-frame is longer, but I think it's again a matter of
scoping; one large project that tries to merge at the end of the summer
is never going to work. It must be broken down into a series of
reviewable steps, and those steps need to be reviewed and merged
throughout the summer, just like contributions from regular
contributors.

Hand in hand with that, I think we need to treat students more like
regular contributors: discussion on-list, patches reviewed and revised
on-list, etc. And all of that happening throughout the summer. Coding is
only part of being involved in open-source, and traditionally the
students have focused on the code and not on the process of interacting
with the community and shepherding their changes through to "master".

Looking over the proposed project page, I am not that excited about any
of them (including ones I have written for past years) as being both
scoped appropriately and interesting/useful for students and for the
project. I think if people want to do GSoC, we really need to make a
commitment to smaller-scoped projects, and to getting students more
involved in the "regular" process of patch submission. The obvious first
step to that is revising the Ideas list to either have smaller projects,
or to break larger ones into more manageable pieces. Unless that
happens, I don't think it's worth applying.

And if we do apply and get accepted, I think we should look carefully at
the proposals that we select, and be very picky about students and
projects that will fit in the summer scope.

I realize that there is only about 48 hours until the deadline, which is
not much. But I am willing to work on the application materials if
people can agree on a reasonable set of proposed projects[2].

-Peff

[1] http://thread.gmane.org/gmane.comp.version-control.git/216485

[2] I have always hoped for students who would submit their own project
    proposals, independent of anything we suggest. After all, that is
    how things happen naturally in open source; contributors scratch
    their own itches. And that is part of why the ideas I post are often
    vague and try to describe a problem rather than a solution. But in
    all our years of GSoC, I recall very few cases of students proposing
    their own projects, and even fewer of them being successful. So I
    have kind of given up hope that we would get any proposal that is
    not spelled out on our ideas page.

Jeff King wrote:

There was a big thread about a month ago on whether Git should do Google
Summer of Code this year[1].

[...]

In my opinion, a lot of the issues come down to project selection;

Let me throw in some other issues. :)

 * I think the git project has been very disorganized in vetting
   candidate students.  Other organizations have formal requirements
   (for example, "must submit at least one properly formatted patch to
   qualify") but we seem to rely on a candidate's good sense,
   independence, and general sense of trustworthiness without
   providing guidance beyond that.

   At first glance that wouldn't seem to be a problem --- the accepted
   students have been very good anyway --- but I think that if we
   could communicate more clearly what we need, we might find there
   are more qualified students that we have been missing, and
   promising students might end up working a little in advance of
   GSoC to adapt themselves to the project.

 * Similarly, we are not very good at making clear the expectations
   for students during the program and making sure they are met.  At
   least I know I was lousy about this as a mentor.

   For example, students delay too long before posting patches
   on-list and do not ask for help quickly when they are stuck.  By
   the end of the summer they may start to get a sense of the usual
   contribution workflow when they could have been more effective
   by following it from the start.

   Some organizations require (as a non-negotiable rule) regular blog
   posts from their students, as a way of advertising to others what
   work they are doing and how to help them out.  That could help
   here. 

 * We didn't plan in advance for "What happens when summer ends and
   the students don't have free time any more?"

 * We don't advertise any good recourse available to students if a
   mentor is unexpectedly too busy or hard to contact.  I don't know
   if that's happened in practice.

Matthieu Moy's summer projects worked better in all these respects, I
think.

I don't think we should apply.  Better to take a break and prepare for
next time.

My two cents,
Jonathan

On Wed, Mar 27, 2013 at 7:52 PM, Jonathan Nieder [off-list ref] wrote:

Jeff King wrote:

quoted

There was a big thread about a month ago on whether Git should do Google
Summer of Code this year[1].

I think we should do it.

It looks strange to me to say that students are great and at the same
time that we should not do it.

Let's give them and us one more chance do to well. This is the only
way we can improve.

Best regards,
Christian.

Jeff King wrote:

There was a big thread about a month ago on whether Git should do Google
Summer of Code this year[1].

Take only one or two students and get the entire community involved in
learning from the GSoC experience, so we can do a bigger one next
year.