Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Mar 2013 23:56:24 +0000 (UTC)
From:      Gavin Atkinson <gavin@FreeBSD.org>
To:        doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org
Subject:   svn commit: r41169 - head/en_US.ISO8859-1/htdocs/internal
Message-ID:  <201303112356.r2BNuOSg043910@svn.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: gavin
Date: Mon Mar 11 23:56:24 2013
New Revision: 41169
URL: http://svnweb.freebsd.org/changeset/doc/41169

Log:
  Minor changes to the page on the new account process:
  - 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

Modified:
  head/en_US.ISO8859-1/htdocs/internal/new-account.xml

Modified: head/en_US.ISO8859-1/htdocs/internal/new-account.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/internal/new-account.xml	Mon Mar 11 21:55:15 2013	(r41168)
+++ head/en_US.ISO8859-1/htdocs/internal/new-account.xml	Mon Mar 11 23:56:24 2013	(r41169)
@@ -109,9 +109,9 @@
   <p>After the new committer confirms that the account works, the mentor
     adds the new committer to the correct <tt>access</tt> file,
     using an appropriate commit message.  The commit message should at least
-    contain the committer's full name, the mentor's name and what area
-    the new committer will start to work in.  For src and doc commit
-    bits, an entry should also be added to the <tt>mentors</tt> file in
+    contain the committer's full name and username, the mentor's
+    name and what area the new committer will start to work in.
+    An entry should also be added to the <tt>mentors</tt> file in
     the respective Subversion repository to indicate
     the mentor relationship. Having done all that,
     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
     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,
-    or via a forced commit to <tt>access</tt> in CVS with an appropriate
-    commit message.</p>
+    community by removing the entry from the <tt>mentors</tt> file in
+    SVN.</p>
 
   <h2>Transfer Of Mentorship</h2>
 
   <p>Should a need arise to transfer mentorship for a committer
     please email the responsible party, as described for a new account
     proposal.  Typically this request is rubberstamped as-is.
-    In Subversion, the <tt>mentors</tt> file should be updated.
-    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>
-
+    In Subversion, the <tt>mentors</tt> file should be updated.</p>
 
   </body>
 </html>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201303112356.r2BNuOSg043910>