Hello Benson,

There is, at least, substantial apathy about git on the part of the 
sub-communities that work on some of the sub-projects. In my view, 
this apathy, including perhaps a bit of antipathy, sunk the discussion 
of just converting as one big repo. As I see it, Felix is a bit of a 
loose confederation, and Ray's suggestion is consistent with letting 
each of the tribes make up its own mind. 
I am not sure if the apathy is related to converting as one big repository.

Let me speak for myself here, I don’t see compelling arguments for moving to 
Git. What problem are we solving here? Why is moving to Git the right solution? 
That’s where my lack of enthusiasm comes from. Nobody has yet explained that to 
me. And splitting the project so each subproject ends up in a different 
repository sounds even less appealing to me (which I am afraid will happen if 
we just start moving one, or a few, subprojects). I would be in favour of a 
plan where we either move every subproject, or none at all. And before we start 
the move, please come up with a plan that outlines the steps that need to be 
taken. Maybe even physically do the migration and demonstrate that things like 
our release processes are still working. And yes, that is a lot of work, and 
enough people need to step up and offer their help.

Greetings, Marcel


Reply via email to