He seems to feel that a Member can create a list and provide oversight.
FWIW, the 'official' policy is documented at:
<http://www.apache.org/dev/list-setup.html>
-- Creating the List
Ask your Project Management Committee to send email to the folks at [EMAIL PROTECTED]
--
and at:
<http://www.apache.org/dev/committers.html>
--
Q: I need to request some changes to infrastructure?
A: You might notice something that needs changing, for example the configuration for a mailing list. The request to the infrastructure@ list or the apmail@ alias needs to come from your Project Management Committee. That ensures that the requests are official, and not just an individual user's desire. This is the same for all requests for infrastructure changes.
--
We've had this conversation before and even codified that requests must come from some 'official' entity not an individual on their own. So, that's our current policy...
And who is going to oversee the new [EMAIL PROTECTED] list that we were asked to do?
As for jobs@, I think the PRC may be the appropriate party to provide oversight to [EMAIL PROTECTED] I'll ping them and see what they think. -- justin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
