Re: questions about PPMCs
Leo Simons wrote: > Martin Sebor wrote: > > I have a few questions about PPMCs that I can't find answers to > > in the documentation. Could someone help me with the answers? > > > > 1. Where do I get the member list for a given PPMC (such as stdcxx)? > > There is a facility for that kind of info that Ken Coar provides at > apache-server.com but I'm a little sketchy on the details. The other one > is to ask apmail at apache dot_goes_here org (there's some ezmlm > commands to enter, see > > http://svn.apache.org/repos/asf/infrastructure/apmail/trunk/README > > ), but apmail is kinda busy so only ask if you've got a really good reason. The facility that Leo refers to is noted in https://svn.apache.org/repos/private/committers/docs/resources.txt There are notes in http://www.apache.org/dev/pmc.html#chair The official list of each PMC is in https://svn.apache.org/repos/private/committers/board/committee-info.txt but i don't know about PPMCs sorry. Moderators can get the list of who is subscribed for any list that they manage by sending to [EMAIL PROTECTED] ...^ > > 2. Who can subscribe to a podling's ppmc mailing list? > > All apache members, all incubator pmc members, and all people on the > PPMC. In addition, it can be ok to invite other people who don't belong > to any of those categories. > > > (If I'm one > >of the moderators of the list, how do I know who to accept and > >who I should reject? -- this is just a hypothetical question). > > There are lists of who is on the incubator pmc (I think in the > committers SVN module) and who are apache members but I honestly don't > know where the most public lists are. There is > > http://people.apache.org/~jim/committers.html > > (people in bold are members). When in doubt, ask. > > > 3. Is any subscriber to the -ppmc list also automatically a member > >of the PPMC? > > no. > > > 4. Are the -ppmc lists archived, and if so, where? > > yes (unless archiving is disabled, which is a Bad Thing). On > people.apache.org (aka minotaur) at > > /home/apmail/private-arch > > in "mbox" format. http://www.apache.org/dev/pmc.html#mail-archives -David > These are good questions and someone should document the answer > somewhere where it can be found. Volunteers welcome :-) > > cheers, > > Leo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: questions about PPMCs
Martin Sebor wrote: > I have a few questions about PPMCs that I can't find answers to > in the documentation. Could someone help me with the answers? > > 1. Where do I get the member list for a given PPMC (such as stdcxx)? There is a facility for that kind of info that Ken Coar provides at apache-server.com but I'm a little sketchy on the details. The other one is to ask apmail at apache dot_goes_here org (there's some ezmlm commands to enter, see http://svn.apache.org/repos/asf/infrastructure/apmail/trunk/README ), but apmail is kinda busy so only ask if you've got a really good reason. > 2. Who can subscribe to a podling's ppmc mailing list? All apache members, all incubator pmc members, and all people on the PPMC. In addition, it can be ok to invite other people who don't belong to any of those categories. > (If I'm one >of the moderators of the list, how do I know who to accept and >who I should reject? -- this is just a hypothetical question). There are lists of who is on the incubator pmc (I think in the committers SVN module) and who are apache members but I honestly don't know where the most public lists are. There is http://people.apache.org/~jim/committers.html (people in bold are members). When in doubt, ask. > 3. Is any subscriber to the -ppmc list also automatically a member >of the PPMC? no. > 4. Are the -ppmc lists archived, and if so, where? yes (unless archiving is disabled, which is a Bad Thing). On people.apache.org (aka minotaur) at /home/apmail/private-arch in "mbox" format. These are good questions and someone should document the answer somewhere where it can be found. Volunteers welcome :-) cheers, Leo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Incubator and Infrastructure
On 9/5/05, David Crossley <[EMAIL PROTECTED]> wrote: > Noel J. Bergman wrote: > > David Crossley wrote: > > > > > I suggest that we go further and make it a requirement > > > of graduation from the Incubator that the project > > > already has some people helping at infra@ > > > > That can only apply if there are ASF Members willing to do it, because we > > don't give apmail or root access to non-Members. And not everyone wants or > > feels competent to manage the tasks. > > > > What tasks did you have in mind? > > Anything. Even just answering other users queries. > That will relieve the other infra people to attend > to the new project's core needs. > > I want to instill at the beginning that we all > need to look after our own ASF - love your Infra. > If you want to participate in a project, then be > prepared to assist with the general infrastructure. > > Leave the rest of this account creation type stuff > to the main infra people ... it's important that every project has committers who are familiar with the apache infrastructure. for example, release management requires knowledge of infrastructure policy which can (at the moment) only be gained by subscribing to the list. so IMO all release managers should subscribe and read the infrastructure list. podlings are going to need release managers. it's better for them to volunteer early so that they have time to (subscribe and) learn. therefore, i'd say that all podlings should have some committers who are subscribed to infrastructure. (hopefully, where they are there, they might find time to submit some documentation patches ;) it's also a question of culture. incubation needs to acclimatize projects to the way that the apache infrastructure team works. the best way to learn this is by subscribing to the infrastructure list. they need to know where to look for information and (if the information is missing) that the right attitude is to volunteer to patch the documents once someone answers the question. a few pmc'er with reasonable knowledge of the apache infrastructure and where to find information are vital in reducing the number of questions that need to be posted to infrastructure. IMHO some of the difficulties with infrastructure have been to do with the slowness of the flow of people from jakarta through to infrastructure. it should be a natural progress from pmc'er to release manager through to being active on the infrastructure list to helping out the infrastructure team. IMO this postive flow needs to be established early for new projects. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
questions about PPMCs
I have a few questions about PPMCs that I can't find answers to in the documentation. Could someone help me with the answers? 1. Where do I get the member list for a given PPMC (such as stdcxx)? 2. Who can subscribe to a podling's ppmc mailing list? (If I'm one of the moderators of the list, how do I know who to accept and who I should reject? -- this is just a hypothetical question). 3. Is any subscriber to the -ppmc list also automatically a member of the PPMC? 4. Are the -ppmc lists archived, and if so, where? Thanks Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Proposal for Tobago, an Apache MyFaces subproject
On 9/5/05, Ted Husted <[EMAIL PROTECTED]> wrote: > On 9/6/05, Martin Marinschek <[EMAIL PROTECTED]> wrote: > > Well, I didn't argument against using the incubator infrastructure. > > > > Nobody seemed too interested here, though (in contradiction to the > > MyFaces community, who was very interested), that's why Ted probably > > thought about going through the MyFaces sandbox directly as a code > > grant is already in place and the licensing issue is very clear. > > > > No problem at all for going through a separate incubator SVN - Ted ? > > > > and thanks for at least some feedback to this proposal ;) > > Perhaps the best thing to do would be to vet just the code through the > incubator. Once the IP is cleared, we can move it to the MyFaces area, > and deal with things like new committers as MyFaces project issues. > I'm not comfortable asking root for new accounts or other resources > under the auspices of the Incubator PMC when we don't have a quorum of > three binding +1s here. I've read the proposal and looked at the current project site. As a member of the Incubator PMC, I'd vote +1 if a vote was needed. However, since it sounds like the MyFaces PMC has already voted to accept the project; so I would suggest that you treat this project like any new incubator project and get accounts set up for each new committer (after CLAs are received). As far as whether just the code goes through incubation or whether the whole community goes through incubation, I think that's a call made by the MyFaces PMC. If the PMC believes that most of the key committers are new to Apache, then they should have the entire project incubated (still not requiring a vote of the Incubator PMC until graduation, under the current rules). If the MyFaces PMC believes that their own community (current set of committers and contributors) can already support the code, then they should just incubate the code and add any outside committers through their normal meritocratic process. Cliff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Incubator and Infrastructure
On Mon, Sep 05, 2005 at 10:30:20AM +1000, David Crossley wrote: > Noel J. Bergman wrote: > > David Crossley wrote: > > > > > I suggest that we go further and make it a requirement > > > of graduation from the Incubator that the project > > > already has some people helping at infra@ > > > > That can only apply if there are ASF Members willing to do it, because we > > don't give apmail or root access to non-Members. And not everyone wants or > > feels competent to manage the tasks. > > > > What tasks did you have in mind? > > Anything. Even just answering other users queries. +1 to having lots of people helping out. But I don't like making these kinds of things required. I rather have the ASF pay for dedicated staff or suffer further degradation of service -- making "volunteering" "mandatory" doesn't feel right. We can do some nudging and nagging and certainly set expectations but I don't like requirements. - LSD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Proposal for Tobago, an Apache MyFaces subproject
On Tuesday 06 September 2005 14:11, Ted Husted wrote: > I'm not comfortable asking root for new accounts or other resources > under the auspices of the Incubator PMC when we don't have a quorum of > three binding +1s here. I am not on the Incubator PMC, but you have have my support anyway ;o) Drop the code into the Incubator, list any particular issues, put up the STATUS page, change license headers (if needed), tick off the items on the STATUS page, then ask the Incubator to Graduate. Can be very smooth. As you mention, committers and such can be handled through the mother project. Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
