I'd like to discuss one detail of the process for new committers.
On May 30, 2007, at 10:56 PM, Craig L Russell wrote:
If the nominee is already an Apache committer on another project, the proposer asks the incubator PMC chair to update the authorization file to include the nominee as a committer on the podling. If the nominee is not already an Apache committer, the incubator PMC member CC's both the Incubator PMC and the PPMC when sending the necessary e-mails to root. Normally, the incubator PMC member is a Mentor on the podling's PPMC but due to unavailability, the proposer can ask any incubator PMC member.
Is it really required for the incubator PMC chair to update the authorization file? Seems like a single point of failure and a possible source of delay. Would it be ok for *any* incubator PMC member with write access to the authorization file to perform this task? There are lots of incubator PMC members with sufficient karma to do the deed.
The issue is probably not a problem on a "normal" PMC since the number of committer requests is low. But the incubator is in charge of dozens of podlings and it seems like this might be a bigger problem here.
Craig Craig Russell DB PMC, OpenJPA PMC [EMAIL PROTECTED] http://db.apache.org/jdo
smime.p7s
Description: S/MIME cryptographic signature
