> > The one thing I can be absolutely sure of is that this PMC > will not be > > involved in disputes about code *ever*. (No, I don't speak for the > > entire PMC.) There will be no 'veto override' and 'veto of last > > resort' or any other such nonsense. If dueling vetos exist, I > > couldn't care less what the PMC says - it's the job of the > committers > > (and the relevant community) to duke it out. > > > I understand where your comming from and in 99.9% of the > cases I think > your right. However, following classic Jakarta rules provides for > deadlocks withing which a hell of a lot of strees can be placed on a > community. Rules provide structure and a framework that > enable rolution > of issues without resorting personal duke-it-out (and the associated > stress) ... I guess I see rules much more like the lines on > a soccer > field - you know where your can go - you know what expected, > whats' not > expected - makes for civilized communities :-) >
Classic jakarta rules classicly suck IMHO. I lurked on httpd-dev and watched Ryan and Greg go at it for months, and I think Apache 2.0 is better for it. If they had 'run to mommy PMC', Apache 2.0 would have aborted, because it would have looked at lot like 1.3. We at jakarta are too thin-skinned sometimes. It all boils down to this: we are all adults, and no other adults should be considered 'more adult'. MHO, of course. Scott
