Committers Agreement: Difference between revisions

no edit summary
(Switch from mozilla.org to The Mozilla Foundation)
No edit summary
Line 4: Line 4:
<b>THIS IS A DRAFT VERSION OF THE AGREEMENT AND SHOULD NOT BE USED</b>
<b>THIS IS A DRAFT VERSION OF THE AGREEMENT AND SHOULD NOT BE USED</b>


In order to obtain the ability to contribute information ("Code") to a Mozilla Foundation source code or data repository and become a "Committer" you must indicate your agreement to the terms below by completing and signing this agreement and returning it to a Mozilla Foundation representative at the address specified at http://www.mozilla.org/hacking/commit/ (the "Notification Address").
In order to obtain the ability to contribute information ("Code") to a Mozilla Foundation source code or data repository and become a "Committer", you must indicate your agreement to the terms below by completing and signing this agreement and returning it to a Mozilla Foundation representative at the address specified at http://www.mozilla.org/hacking/commit/ (the "Notification Address").


=== 1. Contact Information ===
=== 1. Contact Information ===


<b>Name:</b>
<b>Name:</b>
<b>Employer Name:</b><br>
(complete Employer Name if you are committing code to mozilla.org on behalf of your employer)


<b>Email:</b>
<b>Email:</b>
Line 18: Line 15:


<b>Address:</b>
<b>Address:</b>
If you are committing Code on behalf of your employer, then you confirm that an appropriate person at the "Employer Name" above has authorized the inclusion of such Code in the Mozilla Foundation repository under the terms of this agreement.


=== 2. Treatment of Account ===
=== 2. Treatment of Account ===
Line 27: Line 22:
=== 3. License Terms ===
=== 3. License Terms ===


Code committed to the Mozilla Foundation repository must be governed by the mozilla.org tri-license, consisting of the Mozilla Public License ("MPL"), the GNU General Public License ("GPL") and the GNU Lesser General Public License ("LGPL"), or another license or set of licenses acceptable to the Mozilla Foundation. Other licenses are not acceptable to the Mozilla Foundation until the Foundation declares them to be acceptable in writing. Committer will verify that Code contains the appropriate boilerplate licensing text.
Code committed to the Mozilla Foundation repository must be governed by the mozilla.org tri-license, consisting of the Mozilla Public License ("MPL"), the GNU General Public License ("GPL") and the GNU Lesser General Public License ("LGPL"), or another license or set of licenses acceptable to the Mozilla Foundation. Other licenses are not acceptable to the Mozilla Foundation until the Foundation declares them to be acceptable in writing at http://www.mozilla.org/MPL/acceptable/. Committer will verify that Code contains appropriate boilerplate licensing text.


=== 4. Committing Code Created by Others ===
=== 4. Committing Code Created by Others ===
Line 34: Line 29:


a) Committer identifies the author of such Code in a checkin comment that includes the name and email address of the author; and<br>
a) Committer identifies the author of such Code in a checkin comment that includes the name and email address of the author; and<br>
b) To the best of Committer's knowledge, such Code complies with the terms of this agreement.
b) Committer makes reasonable and appropriate efforts to ensure that such Code complies with the terms of this agreement.


=== 5. Cryptography ===
=== 5. Cryptography ===
Line 47: Line 42:
=== 6. Notices and Knowledge ===
=== 6. Notices and Knowledge ===


Committer confirms that, to the best of his/her knowledge:
Committer confirms that, to the best of their knowledge:


a) For any Code using the MPL, any notices required by Sections 3.3, 3.4 or Section 4 of the MPL are included in any Code; and<br>
a) For any Code using the MPL, any notices required by Sections 3.3, 3.4 or Section 4 of the MPL have been appropriately placed; and<br>
b) Code does not violate the rights of any person or entity.
b) Code does not violate the rights of any person or entity.
If Committer contributes Code on behalf of their employer, then they must confirm that an appropriate representative of that employer has authorized the inclusion of such Code in the Mozilla Foundation repository under the terms of this agreement.


<b>Signed:</b>
<b>Signed:</b>
Line 59: Line 56:


----
----
END
<b>END</b>
----
----


=== Open Issues ===
=== Open Issues ===


* Should we maintain the list of acceptable licenses outside of the document, perhaps by referencing the licensing policy?
* Does section 4 need to be stronger - "Committer has made reasonable attempts to verify that such Code complies with the terms of this Agreement"?
* Do we need to better define "a module explicitly identified as containing cryptography"? What does this requirement mean in practice?
* Do we need to better define "a module explicitly identified as containing cryptography"? What does this requirement mean in practice?
Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925

edits