On Friday 25 October 2002 06:15 am, Aaron Bannert wrote: > On Fri, Oct 25, 2002 at 12:32:17AM -0700, Justin Erenkrantz wrote: > > I also don't think that the PMC should set guidelines on a release > > (other than 3 binding +1s) or on coding style or on build systems. > > Leave that up to the committers. > > +1 I agree (on these points) > > > The PMCs job should be to stay the > > heck out of the way of the committers. > > I agree with this, once the PMC has defined a clear mission. > > > If the committers need help, > > they can ask the PMC for guidance, but let's not have a PMC that > > dictates from upon high. > > Dictate is a strong word. I haven't experienced any ASF PMC which > has dictated from upon high. What kinds of things are you worried > about, specifically? > I think it's fear of the unknown. The Jarkarta PMC is very small, and mostly concerned with issues like jarkata top level project creation and oversight of the actions of the committers. The committers make all day to day decisions with little to no reference to the PMC.
In fact, an appeal to the PMC is generally regarded as a failure of the community. Consensus could not be reached, and progress at a standstill. Although, I believe this is in theory, not practice. Software developers are not good at inventing process, we worry far to much about corner cases and exceptional conditions. Necessary in code, not so much when dealing with people.
