...
Any committer who (a) is not already on the PMC, (b) has been a committer for at least 6 months, and (c) has made a commit in the previous 3 months, may be offered an invitation to join the PMC. After a committer becomes eligible, a notice will for discussion can be be sent to the private@ mailing list , and allowed or a vote with the usual 24hrs lazy consensus vote. Assuming that vote passes, the offer should stress what it means to be part of the PMC and that acceptance is an indication that they want to be involved. If they accept the offer, the inviter mails the board informing them of the addition as described here, waits for the necessary 72 hours after the ACK, and assuming no board member objects, they are moved onto the PMCsee the Apache new PMC member instructions before sending an invite to the potential PMC member. There is an Invite template below.
Any PMC member who has become inactive for a period of 6 months (ie. no commits or participation in the PMC/Development community) may be marked as an "emeritus" member of the PMC. At any time, an emeritus member can declare that they are active again, and the emeritus status will be revoked.
...
Be sure to read how-it-works.html – there's lots of useful stuff about ASF processes there.
Invitation Text
No Format |
---|
To: invitee-email-address Cc: private Subject: PMC Member invite from Apache SpamAssassin Dear <Invitee> -- The SpamAssassin PMC has voted to invite you to join as a PMC member! The PMC is the entity that controls the project and speaks for the project. If you accept, you'll have the right to vote for the community-related decisions and the right to propose committer status for active contributors. And, of course, you'll be expected to participate in these community decisions too! The latter needs to be a key factor in your decision to join. It requires almost no effort to serve as a PMC member, but you *are* expected to subscribe to, and keep up with the mailing list traffic on the dev and private lists, provide votes where needed, contribute to the community when it's required, and respect the Apache Way of doing things. Some reading on the subject: http://www.apache.org/foundation/how-it-works.html http://www.apache.org/dev/pmc.html http://www.apache.org/foundation/faq.html http://incubator.apache.org/learn/theapacheway.html If you accept, please reply to that effect, and subscribe to the private@SpamAssassin.apache.org mailing list. ;) |
...