os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Minor changes to the page on the new account process:

Browse source 
- Remove references to CVS, everything is in Subversion now
- The "mentors" file is used in the ports repo, as well as in src/doc
- Commits to "access" should include the new committer's username
This commit is contained in:
Gavin Atkinson 2013-03-11 23:56:24 +00:00
parent 5cb4893dad
commit d0dbb873d9
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=41169
1 changed files with 6 additions and 10 deletions

16
en_US.ISO8859-1/htdocs/internal/new-account.xml
View file

@ -109,9 +109,9 @@
<p>After the new committer confirms that the account works, the mentor <p>After the new committer confirms that the account works, the mentor
adds the new committer to the correct <tt>access</tt> file, adds the new committer to the correct <tt>access</tt> file,
using an appropriate commit message. The commit message should at least using an appropriate commit message. The commit message should at least
contain the committer's full name, the mentor's name and what area contain the committer's full name and username, the mentor's
the new committer will start to work in. For src and doc commit name and what area the new committer will start to work in.
bits, an entry should also be added to the <tt>mentors</tt> file in An entry should also be added to the <tt>mentors</tt> file in
the respective Subversion repository to indicate the respective Subversion repository to indicate
the mentor relationship. Having done all that, the mentor relationship. Having done all that,
the new committer and mentor jointly go through the first commit the new committer and mentor jointly go through the first commit
@ -128,19 +128,15 @@
<p>There is no pre-set duration for a mentorship. Once the mentor feels <p>There is no pre-set duration for a mentorship. Once the mentor feels
the mentee is ready to 'fly solo' the mentor notifies the developer the mentee is ready to 'fly solo' the mentor notifies the developer
community by removing the entry from the <tt>mentors</tt> file in SVN, community by removing the entry from the <tt>mentors</tt> file in
or via a forced commit to <tt>access</tt> in CVS with an appropriate SVN.</p>
commit message.</p>
<h2>Transfer Of Mentorship</h2> <h2>Transfer Of Mentorship</h2>
<p>Should a need arise to transfer mentorship for a committer <p>Should a need arise to transfer mentorship for a committer
please email the responsible party, as described for a new account please email the responsible party, as described for a new account
proposal. Typically this request is rubberstamped as-is. proposal. Typically this request is rubberstamped as-is.
In Subversion, the <tt>mentors</tt> file should be updated. In Subversion, the <tt>mentors</tt> file should be updated.</p>
In CVS, a forced commit to <tt>access</tt> with an appropriate commit
message is to be used to inform the world of the transfer.</p>
</body> </body>
</html> </html>