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. Step 6: Additional review and supervision before merging, in subversion, from that branch across to trunk. I've set this structure up in the read-only direction to facilitate local mods of ICU at our place -- it takes a moderate level of git expertise. On Sat, Oct 3, 2009 at 7:09 AM, Isabel Drost <[email protected]> wrote: > On Friday 02 October 2009 20:49:45 Benson Margulies wrote: > > The ASF git support is good here. You ask infra to set up the clone. > > AFAIK that was already done for Mahout. > > > > Then the students use git svn init. Then they can rebase, make a branch, > and > > package a patch. > > Sounds good enough for me. > > > > A committer still need to commit, but they can downmerge and share > patches. > > Sure, makes sense. > > > Isabel > > -- > QOTD: He who is devoid of the power to forgive is devoid of the power to > love. -- Martin Luther King, Jr. > |\ _,,,---,,_ Web: <http://www.isabel-drost.de> > /,`.-'`' -. ;-;;,_ > |,4- ) )-,_..;\ ( `'-' > '---''(_/--' `-'\_) (fL) IM: <xmpp://[email protected]> > >
