Committers Agreement: Difference between revisions
(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>Email:</b> | <b>Email:</b> | ||
| Line 18: | Line 15: | ||
<b>Address:</b> | <b>Address:</b> | ||
=== 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 | 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) | 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 | 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 | 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 === | ||
* 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? | ||
Revision as of 18:10, 12 February 2007
Mozilla Foundation Committers' Agreement
THIS IS A DRAFT VERSION OF THE AGREEMENT AND SHOULD NOT BE USED
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
Name:
Email:
Phone Number:
Address:
2. Treatment of Account
Committer's Mozilla project account username will be the email address (above) with the '@' character replaces by '%'. Committer will not allow anyone other than Committer to use this account or username to access any Mozilla project system. Should Committer be aware of any such use, Committer will immediately notify the Mozilla Foundation in the manner specified at http://mozilla.org/hacking/commit/; until such notice is received Committer will be presumed to have taken all actions made through Committer's account. The Mozilla Foundation and their designates will have complete control and discretion over capabilities assigned to Committer's account, and may disable Committer's account for any reason at any time. Committer's name and account will be visible worldwide via the Internet.
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 at http://www.mozilla.org/MPL/acceptable/. Committer will verify that Code contains appropriate boilerplate licensing text.
4. Committing Code Created by Others
Committer may check in Code to the Mozilla Foundation repository that was not written by Committer, provided that:
a) Committer identifies the author of such Code in a checkin comment that includes the name and email address of the author; and
b) Committer makes reasonable and appropriate efforts to ensure that such Code complies with the terms of this agreement.
5. Cryptography
Committer understands that cryptographic Code may be subject to government regulations with which the Mozilla Foundation and/or entities using such Code must comply. Any Code which contains any of the items listed below must either be checked-in to a module explicitly identified as containing cryptography, or must not be checked in until the Mozilla Foundation has been notified and has approved such contribution in writing.
a) Cryptographic capabilities or features; or
b) Calls to cryptographic features; or
c) User interface elements which provide context relating to cryptography; or
d) Code which may, under casual inspection, appear to be cryptographic.
6. Notices and 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 have been appropriately placed; and
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.
Signed:
Date:
Printed Name:
END
Open Issues
- Do we need to better define "a module explicitly identified as containing cryptography"? What does this requirement mean in practice?