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

Re: On google summer of code

From: Max Bowsher <maxb1_at_ukf.net>
Date: 2007-03-03 19:09:50 CET

Kristis Makris wrote:
> Hello Subversion developers,
>
> I just noticed Ben's announcement at:
>
> http://subversion.tigris.org/servlets/ReadMsg?listName=dev&msgNo=123911
>
>>From our SCM integration end (and I believe TortoiseSVN needs this too),
> we need the capability in Scmbug to retrieve configuration information
> from the repository:
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=1974
> http://bugzilla.mkgnu.net/show_bug.cgi?id=876
>
> Could this be advertised in your list of ideas that may attract
> students ?

My opinion is no, it cannot, because it is not suitable for a SoC project.

History shows us that this is a problem with an absolutely huge design
quandary hanging over it. As we've been unable to produce a satisfactory
design ready for implementation despite the issue having been around in
the collective conciousness for years, it is not something that can
reasonably be taken as a coding project that needs to be completed on a
fixed deadline.

A valid SoC project needs to be adequately well-defined that we can be
reasonably confident that a skilled programmer could complete it within
the timeframe allowed. The problem with this issue is that we do not
have a final consensus on even a broad outline of an implementation.
There's no guarantee that even with someone dedicated to chairing design
discussions, we'd reach a suitable design with enough time remaining for
it to be implemented within the SoC timeframe.

If an actual design got agreed on, then that would be different, and we
could consider whether that was of suitable scope for SoC, but given
that it hasn't happened yet, I'm not sure that that's at all likely to
happen.

Max.

Received on Sat Mar 3 19:10:24 2007

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.