You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-cvs@jakarta.apache.org by jo...@apache.org on 2001/03/07 23:24:02 UTC
cvs commit: jakarta-site2/xdocs/site roles.xml
jon 01/03/07 14:24:02
Modified: docs/site roles.html
xdocs/site roles.xml
Log:
added more detail based on feedback from sam.
-jon
Revision Changes Path
1.19 +28 -2 jakarta-site2/docs/site/roles.html
Index: roles.html
===================================================================
RCS file: /home/cvs/jakarta-site2/docs/site/roles.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- roles.html 2001/03/07 21:08:09 1.18
+++ roles.html 2001/03/07 22:23:55 1.19
@@ -181,6 +181,10 @@
(ie: John Smith <john.smith@foo.com>)
</li>
<li>
+ Suggested account userid. This is optional.
+ (ie: jmsith)
+ </li>
+ <li>
The project that the user should be given access to.
(ie: Jakarta Foo)
</li>
@@ -190,9 +194,31 @@
</li>
</ul>
<p>
+ Note 0: If a committer already has an account on the apache.org server
+ and the committer needs commit access to additional projects, then all
+ that needs to be done is to have the user notify
+ pmc@jakarta.apache.org with the results of the voting (as documented
+ above) and the user will be given access. In other words, the root
+ email address should only be used on the basis of new account
+ creation.
+ </p>
+ <p>
+ Note 1: All committers will be given access to the jakarta-site module
+ on request. In other words, committers should be able to update the
+ main Jakarta website.
+ </p>
+ <p>
+ Note 2: If the module that the committer needs access to is a sub
+ module within a project (ie: jakarta-turbine-tdk or
+ jakarta-avalon-logkit), it is up to the individual project to
+ determine how to deal with giving out access. In other words, access
+ may be granted by default to all sub modules or it can be granted by
+ vote.
+ </p>
+ <p>
At times, Committers may go inactive for a variety of reasons. A
- Committer that has been inactive for 6 months or more may lose his or
- her status as a Committer. Getting access back is as simple as
+ Committer that has been inactive for 6 months or more may lose their
+ status as a Committer. Getting access back is as simple as
re-requesting it on the projects developer mailing list.
</p>
<p>
1.3 +31 -2 jakarta-site2/xdocs/site/roles.xml
Index: roles.xml
===================================================================
RCS file: /home/cvs/jakarta-site2/xdocs/site/roles.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- roles.xml 2001/03/07 21:08:16 1.2
+++ roles.xml 2001/03/07 22:23:59 1.3
@@ -74,6 +74,10 @@
(ie: John Smith <john.smith@foo.com>)
</li>
<li>
+ Suggested account userid. This is optional.
+ (ie: jmsith)
+ </li>
+ <li>
The project that the user should be given access to.
(ie: Jakarta Foo)
</li>
@@ -84,9 +88,34 @@
</ul>
<p>
+ Note 0: If a committer already has an account on the apache.org server
+ and the committer needs commit access to additional projects, then all
+ that needs to be done is to have the user notify
+ pmc@jakarta.apache.org with the results of the voting (as documented
+ above) and the user will be given access. In other words, the root
+ email address should only be used on the basis of new account
+ creation.
+ </p>
+
+ <p>
+ Note 1: All committers will be given access to the jakarta-site module
+ on request. In other words, committers should be able to update the
+ main Jakarta website.
+ </p>
+
+ <p>
+ Note 2: If the module that the committer needs access to is a sub
+ module within a project (ie: jakarta-turbine-tdk or
+ jakarta-avalon-logkit), it is up to the individual project to
+ determine how to deal with giving out access. In other words, access
+ may be granted by default to all sub modules or it can be granted by
+ vote.
+ </p>
+
+ <p>
At times, Committers may go inactive for a variety of reasons. A
- Committer that has been inactive for 6 months or more may lose his or
- her status as a Committer. Getting access back is as simple as
+ Committer that has been inactive for 6 months or more may lose their
+ status as a Committer. Getting access back is as simple as
re-requesting it on the projects developer mailing list.
</p>