Re: [Tuxpaint-devel] Hello and SCM question
An award-winning drawing program for children of all ages
Brought to you by:
wkendrick
|
From: Mark K. K. <mkk...@gm...> - 2008-04-24 01:44:41
|
On Wed, Apr 23, 2008 at 05:54:50PM -0400, Reilly Watson wrote: > I was wondering how you guys wanted to handle we students regarding CVS. > Did you just want to give us all write access (my SF username is > reillywatson), did you want us to submit changes to (this list|our > mentors|some whole other place) for review, or would you like that to be > negotiated individually between each student/mentor pair? I have a few > things written that are (I think) ready to go. We already had a discussion about this (surprise surprise!) and most of the mentors feel that it would not be prudent to give new contributors write access immediately. Other than that we left it up to the student/mentor pair to decide how to proceed. For my student and I, we will be using a new repository on code.google.com. There are several benefits to this: 1. We can still use a version control system, which will be useful for new OSS contributrs to learn. 2. Google should be more willing to offer up their repository since they sponsor GSoC. Souceforge and Savannah would not likely allow us to create new repositories just for a summer. 3. We will be using Subversion rather than CVS =) 4. Most importantly, the student's work will be kept in one place, so it will be easier to submit a single diff at the end of the summer, required by GSoC. Obviously, at the end of the summer, if we feel that the patch is beneficial (which is most likely), we will merge the patch into the main branch and give the student a write access to continue to develop on Tux Paint. -Mark |