+1 I think moving to Git would eventually simplify a few things. Especially ramping up new committers and sporadic contributors will likely find it easier through Git. Robert already brought up some issues we need keep in mind when migrating and I'm sure there are more. Let's see whether we can get a rough consensus first on whether we want to move in the next couple of months before delving too deep into technical issues.
Michael On Mon, 10 Dec 2018 at 11:45, Robert Munteanu <romb...@apache.org> wrote: > > Hi Francesco, > > On Mon, 2018-12-10 at 10:58 +0100, Francesco Mari wrote: > > Given the recent announcement about gitbox.apache.org, the seamless > > integration with GitHub, and the fact that many of us already work > > with Git > > in our daily workflow, what about moving our repositories to Git? > > Well, I'm all for it, but there are many details to be filled in ... > > - one repository for Oak or one repository per module (oak-commons, > oak-api, etc )? > - how does this tie into the potential modularisation work? > - who will do the work for migrating repositories, release scripts, > Jenkins setup, etc? > - what is the transition plan for the SVN repositories and what will > happen to the existing github mirrors? > > (and probably some I'm missing) > > Thanks, > > Robert >
