On Fri, 30 Sep 2005, David Plans Casal wrote:
seems like i can finally get rid of the "mr. rude and grumpy" award...
i didn't wanted to sound rude ... but personally i don't have any
of course. neither did i want to sound rude or grumpy when i eventually did so...
Just 2eurocents from a devel_0.39 -and- MAIN user...my guess is we're going to talk about forking here, at today's IRC meeting, right?
There hasn't been that much talking about forking the project at the meeting. Anyway I don't think it's really a topic in itself: it's implicit that if we don't communicate (between the Millers and the nonMillers among us) then the crack in the floor will widen faster than if we don't.
However, the crack in the floor will continue widening until Miller gives up gatekeeping his branch alone.
I've seen forks in other FLOSS projects, and they're never pretty.
But are they necessary? If they're necessary, then whether they're pretty or not is not a question.
May I suggest, that while we consider these issues, we also consider the appointment of a release manager? I know that Tim's work on dev39 is almost nominally exactly that, but I feel that someone should take on the actual release manager role, since that would almost certainly help the fork-like feelings and problems here, no?
Now the question is: what will the release manager do when Pd/MSP 0.40 comes out? Because I'm not certain at all what Tim will/would do with a Pd/MSP 0.40 on his hands.
And then I wonder who would volunteer for merging stuff while not dropping any features from either branch.
What else should the release manager do? There could be "stabilized" versions of the devel branch, that is, for each big release, a branch made only for bugfixes, but I don't think we can afford that luxury right now, unless someone volunteers for that, and that's certainly not certain.
____________________________________________________________________ Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju Freelance Digital Arts Engineer, Montréal QC Canada