Committers Agreement: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Initial version; retyped copy of http://www.mozilla.org/hacking/CVS-Contributor-Form.pdf)
 
(Correct license policy URL to use same URL as current license policy)
 
(22 intermediate revisions by 6 users not shown)
Line 1: Line 1:
__NOTOC__
__NOTOC__
== mozilla.org CVS Contributor Form ==
== Mozilla Foundation Committers' Agreement ==
{{draft}}
<b>THIS IS A DRAFT VERSION OF THE AGREEMENT AND SHOULD NOT BE USED. There is a [[Committers_Agreement:Changelog|list of changes]]. For more information see [https://bugzilla.mozilla.org/show_bug.cgi?id=342029 bug 342029].</b>


<b>For Committing Code To The mozilla.org CVS Source Repository</b>
In order to become a Committer - that is, to obtain the ability to contribute information ("Code") to a Mozilla Foundation source code or data repository - you ("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 [[Committers_Agreement:Notification|http://www.mozilla.org/hacking/notification/]] (the "Notification Address").
 
In order to obtain the ability to commit changes to a mozilla.org CVS source 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/form.html (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 17: Line 14:
<b>Phone Number:</b>
<b>Phone Number:</b>


<b>Address:</b>
<b>Postal 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.org source repository under the terms of this agreement.


=== 2. Treatment of Account. ===
=== 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 CVS 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/form.html; 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.
You will receive one or more sets of Mozilla project access credentials. You will not allow anyone else to use these credentials to access any Mozilla project system. Should You become aware of any such use, You will immediately notify the Mozilla Foundation in the manner specified at [[Committers_Agreement:Notification|http://www.mozilla.org/hacking/notification/]]; until such notice is received You will be presumed to have taken all actions made using Your credentials. The Mozilla Foundation and their designates will have complete control and discretion over capabilities associated with Your credentials and may change them for any reason at any time. Your name and email address, or a derivative of it, may be visible worldwide via the Internet.


=== 3. License Terms. ===
=== 3. License Terms ===


Code committed to the mozilla.org CVS source repository ("Committed Code") must be governed by the Netscape Public License ("NPL"). Mozilla Public License ("MPL") or aother license acceptable to mozilla.org. Committer will verify that Committed Code contains the text of Exhibit A of the MPL or NPL, or another license acceptable to mozilla.org. Other licenses are not acceptable to mozilla.org until mozilla.org declares them to be acceptable in writing.
Code committed to a 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 for the Code in question. Other licenses are not acceptable to the Mozilla Foundation until the Foundation declares them to be acceptable in writing at [[License_Policy|http://www.mozilla.org/MPL/license-policy.html]]. You will verify that committed Code contains appropriate boilerplate licensing text.


=== 4. Committing Code Created by Others. ===
=== 4. Committing Code Created by Others ===


Committer may check in code to the mozilla.org CVS source repository that was not written by Committer, provided that:
You may check in Code to a Mozilla Foundation repository that was not written by You, provided that:


a) Committer identifies the author of such code through a comment in the CVS log that includes the name and email address of the author; and<br>
a) The checkin comment contains information (or references to information) sufficient to identify the author of the Code, including at minimum an email address; and<br>
b) To the best of Committer's knowledge, such code complies with the terms of this agreement.
b) You make all reasonable and appropriate efforts to ensure that such Code conforms to the terms of this agreement.


=== 5. Cryptography. ===
=== 5. Cryptography ===


Committer understands that cryptographic code may be subject to government regulations with which mozilla.org and/or entities using Committed 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.
You understand 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<br>
a) Cryptographic capabilities or features; or<br>
Line 45: Line 40:
d) Code which may, under casual inspection, appear to be cryptographic.
d) Code which may, under casual inspection, appear to be cryptographic.


=== 6. Notices and Knowledge. ===
=== 6. Notices and Knowledge ===


Committer confirms that, to the best of his/her knowledge:
By contributing Code, You confirm that, to the best of Your knowledge:


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


<b>Signed:</b>
<b>Signed:</b>
Line 57: Line 54:


<b>Printed Name:</b>
<b>Printed Name:</b>
----
<b>END</b>
----
=== Open Issues ===
* Do we need to better define "a module explicitly identified as containing cryptography"? What does this requirement mean in practice?

Latest revision as of 20:51, 9 May 2008

Mozilla Foundation Committers' Agreement

Draft-template-image.png THIS PAGE IS A WORKING DRAFT Pencil-emoji U270F-gray.png
The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly.
If you have any questions or ideas, please add them as a new topic on the discussion page.

THIS IS A DRAFT VERSION OF THE AGREEMENT AND SHOULD NOT BE USED. There is a list of changes. For more information see bug 342029.

In order to become a Committer - that is, to obtain the ability to contribute information ("Code") to a Mozilla Foundation source code or data repository - you ("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/notification/ (the "Notification Address").

1. Contact Information

Name:

Email:

Phone Number:

Postal Address:

2. Treatment of Account

You will receive one or more sets of Mozilla project access credentials. You will not allow anyone else to use these credentials to access any Mozilla project system. Should You become aware of any such use, You will immediately notify the Mozilla Foundation in the manner specified at http://www.mozilla.org/hacking/notification/; until such notice is received You will be presumed to have taken all actions made using Your credentials. The Mozilla Foundation and their designates will have complete control and discretion over capabilities associated with Your credentials and may change them for any reason at any time. Your name and email address, or a derivative of it, may be visible worldwide via the Internet.

3. License Terms

Code committed to a 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 for the Code in question. 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/license-policy.html. You will verify that committed Code contains appropriate boilerplate licensing text.

4. Committing Code Created by Others

You may check in Code to a Mozilla Foundation repository that was not written by You, provided that:

a) The checkin comment contains information (or references to information) sufficient to identify the author of the Code, including at minimum an email address; and
b) You make all reasonable and appropriate efforts to ensure that such Code conforms to the terms of this agreement.

5. Cryptography

You understand 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

By contributing Code, You confirm that, to the best of Your knowledge:

a) For any Code contributed under MPL terms, 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 You contribute Code on behalf of Your employer, then You must confirm that an appropriate representative of that employer has authorized the inclusion of such Code in a 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?