On Sat, Oct 3, 2009 at 11:19 AM, Grant Ingersoll <[email protected]>wrote:
> > On Oct 3, 2009, at 10:11 AM, Benson Margulies wrote: > > There is one further level of fun available here. >> >> Step 1: committer makes svn branch. >> >> Step 2: verify/arrange that branch is included in git clone. >> >> Step 3: set up served git clone of that branch at your place with gitosis >> or >> whatever. Note that git svn doesn't do 'bare', but it doesn't turn out to >> interfere. >> >> Step 4: students actually commit to that clone. >> >> Step 5: committer pushes that up to ASF svn on the branch with light >> supervision. >> >> > I'm not sure the ASF treats branches any differently from trunk when it > comes to the supervision involved. > Let me clarify. Anything that goes into the real ASF repo has to come from someone with an iCLA, and a committer has at least to be confident that there isn't someone else's IP involved. Beyond that, we're in the territory of the particular's community's taste in patch control. Piling up a bunch of contributions in a branch is, in my view, just another alternative to stacking them up in JIRAs. If you are anticipating a large volume of contributions from this project, you might find my Rube Goldberg contraption attractive.
