On Tue, Dec 1, 2015 at 11:43 AM, Marcel Offermans <marcel.offerm...@luminis.nl> wrote: > 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.
That's not what I was trying to express. There are some people who, like you, are not enthusiasts. (I'm not interested in trying to convince anyone else that git is 'better'. I will only write that git is becoming very popular, and, as a result, it can facilitate community growth to use it.) Thus, if you ask the question, 'should we move the whole Felix tree to git?', it could be that there are enough non-enthusiasts to block consensus. That is my proposed explanation for the death of the previous thread. And maybe it should just stay dead. If the community has no consensus to move to git, it stays in svn. Ray's proposal looks at another perspective, which is that Felix is composed of a set of rather loosely-coupled pieces. If the predominant contributors to some of those pieces want them in git, why not? (I appreciate that Marcel's view is an answer to the question 'why not!') I offer as an analogy, 'some things build with Maven, some with Gradle.' Since we don't release the entire tree at once, I don't why the choice of VCS needs to be any more uniform than the choice of build tool. However, I didn't reopen this question today to fill everyone's mailbox. I'd like to maintain the bundle plugin in git. But I'm not going to stomp off in a huff if doesn't happen. I'd be happy to see a vote to move just the bundle plugin, and I'll live with the outcome either way. Same for a vote to proceed with the whole project. But if the right thing to do is ... nothing ... then nothing it is. > > 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 > >
