Committers Agreement

mozilla.org Contributor Form

For Committing To The mozilla.org Repositories

THIS IS A DRAFT VERSION OF THE FORM AND SHOULD NOT BE USED

In order to obtain the ability to contribute information ("Code") to a mozilla.org 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 mozilla.org at the address specified at http://www.mozilla.org/hacking/commit/ (the "Notification Address").

1. Contact Information

Name:

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

Email:

Phone Number:

Address:

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.org repository under the terms of this agreement.

2. Treatment of Account

Committer's mozilla.org 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 a mozilla.org repository or other mozilla.org systems. Should Committer be aware of any such use, Committer will immediately notify mozilla.org 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. mozilla.org 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.org 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 mozilla.org. Other licenses are not acceptable to mozilla.org until mozilla.org declares them to be acceptable in writing. Committer will verify that Code contains the appropriate boilerplate licensing text.

4. Committing Code Created by Others

Committer may check in Code to the mozilla.org 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) To the best of Committer's knowledge, such Code complies with the terms of this agreement.

5. Cryptography

Committer understands that cryptographic Code may be subject to government regulations with which mozilla.org 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 mozilla.org module explicitly identified as containing cryptography, or must not be checked in until mozilla.org staff 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 his/her 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
b) Code does not violate the rights of any person or entity.

Signed:

Date:

Printed Name:

---

END

---

Open Issues

• Do we still need the crypto section?
• Should people now be making an agreement with the Mozilla Foundation?
• 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"?