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

Will subversion participate in Google Summer of Code 2010?

From: Daniel Näslund <daniel_at_longitudo.com>
Date: Sun, 21 Feb 2010 14:11:35 +0100


Google Summer of Code is on for 2010 [1]. Is there any interest in
participating this year? If so, I've found that the mentoring
application deadline is 12 march. [2]

Since we're part of ASF, perhaps an application should go
through them? [3]

I've tried locating the GSoC ideas pages for 2009 but it seems to have
got lost in the move to apache.org. My own suggestions (given what I
know of subversion so far) would be:

Implementing a tree conflict resolver
This task probably should have editor-v2 available. Perhaps the task
could be defined as doing some vital parts of editor-v2 and continue
with a TC resolver once finished with the editor. And yes, I have no
notion whatsoever about the time frame required for the editor-work.

Replacing externals with something similar of ClearCases views
I overheard a conversation between Senthil and Bert on IRC where Bert
mentioned the views concept of ClearCase. [4] I want something like
externals but without the edge cases of file externals and with the
externals nodes being more like regular nodes.

Patch queues
Some kind of quilt functionality for local storage of work-in-progress.
Probably needs to have most the WC-NG parts stable.

The views concept and TC resolver was in the GSoC 2009 ideas page IIRC.

If the subversion community is interested in participating, I'm looking
forward to compete in a friendly fashion for one of the Student
Developer positions.


[1] http://code.google.com/soc/
[2] http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#timeline
[3] http://community.apache.org/gsoc.html
[4] http://techpubs.sgi.com/library/dynaweb_docs/0620/SGI_Developer/books/ClrC_CG/sgi_html/ch04.html
Received on 2010-02-21 14:12:16 CET

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