Contribution Process


All contributors (and committers) following the managed model (see here) need to use this contribution process. The terms 'contributor' and 'committer' are defined here.

Here are the steps to becoming a contributor:


1. All contributors need to be registered (see here).


2. If the contributor's employer is an OpenNTF member:
Send a mail to IP-manager@openntf.org with your signature that you'll follow the contribution process and guidelines.

You should copy/paste the following text into an email message, substitute your name, email address and Member company name into the appropriate fields, and transmit the email:
<<
My name is <your-name>.
My email address is
<email-address>.
I am employed by the following organization:
<company-name>.
I wish to become a Contributor to the OpenNTF Alliance. My employer is a Member of OpenNTF Alliance. I confirm that all of my Contributions will be on behalf of my employer. I confirm my understanding that my employer has signed the OpenNTF Alliance Members Agreement, and thus has agreed to the OpenNTF Alliance IPR Policy that is contained in this agreement. I confirm that I (or other employees of my employer) will be the original author of all Contributions that I will be submitting or that I (or other employees) will clearly identified those portions of the Contribution that are not our original creation, and will provide information on its origin (such as a previous OpenNTF contribution).

>>
Then await confirmation and acceptance from the project administrators.


3. If the contributor's employer is not an OpenNTF member:
Send a mail to IP-manager@openntf.org with 1. your employer's consent that you may contribute code to OpenNTF and 2. with your signature that you'll follow the contribution process and guidelines.

Copy/paste the following text into a text editor, substitute your name, and email address:
<<
My name is <your-name>.
My email address is
<email-address>.

I wish to become a Contributor to the OpenNTF Alliance. All of my Contributions are on behalf of myself. I agree that my contributions are subject the
OpenNTF Alliance IPR policy. I confirm that I will be the original author of all Contributions that I will be submitting or that I will clearly identified those portions of the Contribution that are not my original creation, and will provide information on its origin (such as a previous OpenNTF contribution).
>>

Then you need to do the following:
  • Print the message to create a hardcopy.
  • Sign the hardcopy.
  • Fax the two signed hardcopies to +1-845-491-7347 or email a scan of the two hardcopies to IP-manager@openntf.org.
  • Then await confirmation and acceptance from the project administrators.


4. Join a project as contributor

Send a communication to the primary project owner that you wish to become a contributor and that you understand and acknowledge that all of your contributions will be in conformance with the OpenNTF Alliance IPR Policy.
You will be assigned a committer The committer will have the access rights to add your contribution to the OpenNTF repository.


Committers and committer responsibilities

Committer appointment/election: Individuals, who have completed the requirements of the OpenNTF Alliance Contribution Process (see above) may be appointed as committers by the Steering Committee, or elected as a committer by a majority vote of existing committers.

Committer due diligence: Before any contribution may be added to any OpenNTF Project, the committer must be satisfied that the following conditions have been met:

a) the contribution has been submitted by a contributor who has completed the requirements of the Contribution Process;

b) there is no indication of that any portion of the contribution comes from a party other than the contributor, and that either a visual scan or automatic code scan has been done to confirm this:

c) the Apache license information (see here) has been included appropriately in the code; and

d) there is no encryption content in the code.

If one of the conditions is not met, the committer will work with the Steering Committee (or delegate thereof) to resolve the issues. The resolution may take the form of, without limitation, approving third party content in the code, approving a license other than the Apache License Version 2, ensuring that encryption code is handled according to appropriate laws, or rejection of the contribution.

The committers shall maintain a record, for each project, of each contributor to that project.