code review 157158: change the rules for maintaining AUTHORS and CONTRIBUTO...

doc/contribute.html

 <!-- Contributing to the Go project -->
 
 <h2 id="Introduction">Introduction</h2>
 
 <p>
 This document explains how to write a new package,
 how to test code, and how to contribute changes to the Go project.
 It assumes you have installed Go using the
 <a href="install.html">installation instructions</a>.  (Note that
 the <code>gccgo</code> frontend lives elsewhere;
@@ skipping 316 matching lines @@
         src/pkg/math/sin.go
         src/pkg/math/tan.go
         src/pkg/regexp/regexp.go
 </pre>
 
 <p>
 The <code>Reviewer</code> line lists the reviewers assigned
 to this change, and the <code>CC</code> line lists people to
 notify about the change.
 These can be code review nicknames or arbitrary email addresses.
+If you don't know who is best to review the change, set the
+reviewer field to the
+<a href="http://groups.google.com/group/golang-dev">golang-dev@googlegroups.com</a>
+mailing list.
 </p>
 
 <p>
 Replace &ldquo;<code>&lt;enter description here&gt;</code>&rdquo;
 with a description of your change.
 The first line of the change description is conventionally
 a one-line summary of the change and is used as the
 subject for code review mail; the rest of the
 description elaborates.
 </p>
@@ skipping 283 matching lines @@
 If you are the copyright holder, you will need to agree to
 the <a href="http://code.google.com/legal/individual-cla-v1.0.html">individual
 contributor license agreement</a>, which can be completed online;
 if your organization is the copyright holder, the organization
 will need to agree to the <a href="http://code.google.com/legal/corporate-cla-v1.0.html">corporate contributor license agreement</a>.
 (If the copyright holder for your code has already completed the
 agreement in connection with another Google open source project,
 it does not need to be completed again.)
 <li>
 Send mail, or include information in the change list description,
-notifying us how you should
-be represented in the <code>CONTRIBUTORS</code> and <code>AUTHORS</code>
-files so we can add your information to them.

[rsc, 2009/11/24 21:55:57]

Specifically, tell us either that you've completed out the individual agreement
or tell us the name of your organization once it has completed the
corporate agreement.  One of the Go developers at Google will add you
to CONTRIBUTORS and, if appropriate, AUTHORS after verifying that the
agreement has been completed.  We will use the email address you use
on codereview.appspot.com as the email address in these files.

-</ol>
+notifying us how you should be represented in the <code>CONTRIBUTORS</code>
+and <code>AUTHORS</code> files so we can add your information to
+them.  Specifically, tell us either that you've completed the
+individual agreement or tell us the name of your organization once
+it has completed the corporate agreement.  One of the Go developers
+at Google will add you to <code>CONTRIBUTORS</code> and, if
+appropriate, <code>AUTHORS</code> after verifying that the agreement
+has been completed.  We will use the email address you use on
+codereview.appspot.com as the email address in these files.</ol>
 <p>
 This rigamarole needs to be done only for your first submission.
 </p>
 
 <p>
 Once the code is ready to be committed,

[rsc, 2009/11/24 21:55:57]

i think you can delete this in favor of the above.

[r1, 2009/11/24 21:59:25]

i don't think so. this says that *we* will do the committing. that's not said
elsewhere.

 one of the Go developers at Google will approve and submit
-your change after checking that the items above have been executed.
-</p>
+your change.
+</p>