I do agree with every point of the proposal - but I can't be fully +1 until the non-normative guidelines are well defined.
I believe everyone who is actively developing code and participate in jakarta should have the option ( and be encouraged ) to be in the jakarta PMC. That's the goal ( IMO ). The protection of the PMC matters the most for those who actually write code and actively participate in jakarta. The 'management' part of the PMC should be done by the same people. By 'active' I mean commits of any kind, mailing list participation, vote participation, review of other people commits, etc. Everyone can decide for himself if he feels 'active' - and _volunteer_ for the PMC. The PMC can vote on this ( I think a majority vote is the best - or lazy consensus followed by a majority vote if any issue ). I also think people who don't feel 'active' should be encouraged by the non-normative guideline to change their status to 'emeritus'. This way ASF and anyone else will know that the (active ) PMC members are indeed the people who make all the decisions and monitoring. This form of PMC could also increase the links and synergies among jakarta projects and the sense of community. Costin On Mon, 2002-11-04 at 00:52, Sam Ruby wrote: > I'm planning on submitting a proposal to change the bylaws of Jakarta to > bring Jakarta's PMC structure closer to the HTTPD one. Before I do so, > I would like to gather the opinions of a self selecting cross section of > both Jakarta and non-Jakarta committers, and it occurs to me that this > mailing list enables me to do exactly that. > > My intent is not to rush to put in place any radical change, or to > address all issues in one sweeping proposal. My intent is merely to put > in place enough bylaws to enable the necessary changes to be made. My > current thinking is to propose this formally after the ApacheCon to give > people adequate time to discuss this, but feedback on both the content > and timing are welcome. > > Enough preamble. Here's the outline of the proposed changes: > > 1) Eliminate any upper limit to the number of PMC members > > 2) Allow new PMC members to be proposed at any time > > 3) Remove references to resigning, add an emeritus status > > 4) Reinstate all past PMC members as emeritus status > > In addition to these bylaws, I anticipate a set of non-normative > guidelines. Proposed PMC members will normally already be committers. > Typically, a proposed PMC member will have been actively involved on a > sustained basis (no significant gaps) for six months since becoming a > committer. I intend to nominate any ASF members who are also Jakarta > committers as new PMC members. > > The intent is that this is intended to be orthogonal to any proposals to > promote an existing Jakarta subproject to become a top level project. > Of course, people involved may voluntarily chose to change their status > to emeritus, but are under no obligation to do so. > > Thoughts? > > - Sam Ruby > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
