On 12/1/15 13:40 , Carsten Ziegeler wrote:
Richard S. Hall wrote
Well, the argument to the contrary is perhaps that is makes it more
difficult for us as a community to have oversight into releases. It
almost assures us that some/many community members will never checkout
subprojects that aren't in the repository they normally work. Granted,
there is no guarantee of this now, since I can just check out what I
want anyway...but at least it is fairly easy for me to do so now and it
becomes more difficult if everyone spreads to their own repos.
So, in that regard, I'm more aligned with Marcel...all or nothing makes
more sense.
Hmm, ok fair point - however, the *all* is the problematic part where we
couldn't agree on last time (one git repo vs many git repos).
But isn't it then incumbent on those wanting such changes to convince us
one way or the other?
Personally, I'd rather just have one big git repo if we are going to
switch, if for no other reason than it seems like less overhead.
However, I admit to not really knowing the advantages/disadvantages.
Regardless, at a minimum, perhaps someone should create a documented
pros/cons list for the approaches. This would at least give us a way to
call a vote where we can feel somewhat informed about the choices (i.e.,
stay with svn, move to one git repo, move to many git repos).
Better than saying, "there is no consensus, so let's just go our
separate ways"...
-> richard
We could still provide a script in the root of svn which checks out the
moved projects from git and gives the same experience :)
Carsten
