qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-24 23:07:56 -07:00
Code Releases Activity

change the rules for maintaining AUTHORS and CONTRIBUTORS files.

Browse Source 
the current system is too painful, so instead let's just have the coders tell us the details.
we can update the files ourselves.

R=rsc, r1
CC=golang-dev
https://golang.org/cl/157158
This commit is contained in:
Rob Pike 2009-11-24 14:04:43 -08:00
parent 001a8b11ff
commit 2cbeb1dbb1
1 changed files with 27 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
doc/contribute.html
View File

@ -626,20 +626,36 @@ who “The Go Authors”—the copyright holders—are.
</p> </p>
<p> <p>
When sending your first change list, you should prepare When sending your first change list, you need to do two extra things before your
and send a separate change list adding yourself to code can be accepted.
<code>CONTRIBUTORS</code> and adding </p>
the copyright holder for your code to <code>AUTHORS</code> if not already listed. <ol>
<li>
If you are the copyright holder, you will need to agree to 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>, the <a href="http://code.google.com/legal/individual-cla-v1.0.html">individual
which can be completed online; contributor license agreement</a>, which can be completed online;
if your organization is the copyright holder, the organization 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>. 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 (If the copyright holder for your code has already completed the
agreement in connection with another Google open source project, agreement in connection with another Google open source project,
it does not need to be completed again. it does not need to be completed again.)
One of the Go developers at Google will approve and submit <li>
this change after checking the list of people/organizations Send mail, or include information in the change list description,
that have completed the agreement. 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>
<p>
Once the code is ready to be committed,
one of the Go developers at Google will approve and submit
your change.
</p>