[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: GSOC Project ideas

From: Hyrum K Wright <hyrum_at_hyrumwright.org>
Date: Fri, 18 Mar 2011 15:20:32 -0500

On Fri, Mar 18, 2011 at 3:00 PM, Mark Phippard <markphip_at_gmail.com> wrote:
> On Fri, Mar 18, 2011 at 3:51 PM, Ivan Zhakov <ivan_at_visualsvn.com> wrote:
>> On Fri, Mar 18, 2011 at 22:46, Mark Phippard <markphip_at_gmail.com> wrote:
>>> Something that came up on the list recently was adding support for
>>> pipelined commits via ra_serf. Would this make a good GSOC project?
>>> It seems like the kind of "engineering" challenge that might appeal to
>>> a student.  I have no idea if it is too big or small for GSOC.  For
>>> example, I have no idea if this is something that can be done with
>>> just changes to our client or if it also requires modifying
>>> mod_dav_svn.
>> I don't think that's a good idea for GSoC project, because
>> ra_serf/serf currently not so stable and developing new feature can
>> destabilize it completely.
> With this planned to become our new default in 1.7, I am going to
> pretend I did not read this :)
> This work should all happen on branches anyway and we need to get a
> lot less averse to doing work on branches.

We can discuss the general merits of branches vs. trunk at some point,
but for GSoC, I'd like to see as much of the work on trunk as
possible. One of the goals of the program is to encourage new
contributors, and seeing their work go onto trunk is much more likely
to achieve that end than seeing it languish on a branch forever.

I'm *not* saying we give people a pass and grant them carte blanche to
trunk just for being an SoC student, but we ought to think about how
to help get them there as fast as possible.

Received on 2011-03-18 21:21:04 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.