On Tue, 22 Oct 2002, Costin Manolache wrote: > We already have a line in our charter about having a jakarta-commons > specific PMC. Right now it is modeled after jakarta, with 3 > members.
Has this been confirmed as legal according to the Apache rules? Using the name PMC. Or is it just that we can call it PMC but it's not recognised by the board as an actual Project PMC? > I would like to propose changing this number to include more > people - I think the right solution is more closer to what httpd > and apr projects are doing, where the PMC is composed of most > active commiters. > > My proposal is to modify the charter so that a jakarta-commons PMC > is composed of all active commiters. This will be volunteer-based, > in the sense that any active commiter who wants to become > part of the PMC will announce his willingness to participate. > > Questions: > - should we vote on the volunteering offer ? What is httpd doing ? > - Should we impose a 2-3 month wait period for new commiters ? ) > - should the pmc have a separate mail list ? ( I personally don't > think so - but that's how other pmcs are organised ) All good questions. Having a separate mail list seems unnecessary given the current mode of self-management for the project, so the only reason for the mail list I can think of is if an external body [say the Jakarta PMC] needed to talk to the pmc. As part of the reason for this [I imagine] is due to criticism from non-Jakarta members concerning the loose management structure in Jakarta, then taking a good look at the httpd structure would be good. Do they nominate for pmc or volunteer etc. How inactive is someone before they leave/pushed from the pmc. A wait on new committers seems a good ideas. If a nnew codebase joined [without incubating] then I could see a reason why that codebase should have a member on the pmc, but maybe it should be that a current pmc person should be on their codebase. > The commons PMC members will split the task of monitoring the > files. All decisions will continue to be taken by majority > vote of all jakarta-commons commiters. > > Not that this is not a proposal to form a top-level project - > just to better organise ourself. Jakarta-commons is IMO at the > core of jakarta - with the most diverse set of commiters from > almost all jakarta projects. Any major issue will be forwarded > to the Jakarta PMC. Seems good. Hen -- To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org>
