- Access control is via /x1/svn/asf-authorization. We would need to add the following:
avalon=<all committers> [in the groups area]
[/avalon] @avalon = rw
"We", Berin, means you (although I can if you ask).
This configration does not provide fine-grained access control. I believe that the philosophical approach is that if you a Committer, you get access. This is one Project. If necessary, we can provide additional levels of control, e.g., if we wanted to give someone karma for the site without the code, or if we had some need for a PMC-only area. Details in http://svn.collab.net/repos/svn/trunk/subversion/mod_authz_svn/INSTALL.
One question though. We have the component repositories set up so that there is a greater access to both the James and Cocoon developers. All Avalon developers should have access to all Avalon repositories, but we would only want the Cocoon and James developers to have access to the component repositories. The main reason being is that if they wanted to affect a change to the containers/framework then it should be a community effort. They may eventually become Avalon developers, or they may simply work with the existing Avalon community.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
