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? > Note that as a committer I have very rigid requirements for what a > release is, what coding style, and what build system to use. But, I > don't believe the PMC should dictate to *me* what tools I use. (One > reason I'm against using Ant commons-wide - it sucks for C code which > is about all I care about.) -- justin +1 :) -aaron
