Jump to: navigation, search

Difference between revisions of "IAM Contributions"

(Summary of the IP process)
 
(Provide template for getting IP answers on bugzilla)
 
Line 7: Line 7:
 
* Committers can commit :-).
 
* Committers can commit :-).
 
* Non-committers (contributors) need to attach the contributions to a bugzilla.  
 
* Non-committers (contributors) need to attach the contributions to a bugzilla.  
 +
 +
In any case, '''contributors must answer the following questions''' (provided for cut&paste in bugzilla, derived from the [http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf IP poster]):
 +
{{CommentBox|
 +
We need acknowledgment that the provided patches:
 +
* Do not contain cryptography
 +
* Are developed from scratch (does not contain IP from others)
 +
* Are 100% EPL
 +
This is for all content, including XMLs, DTDs, iamges...
 +
}}
  
 
== Small contribution ==
 
== Small contribution ==

Latest revision as of 16:04, 26 November 2008

< To: IAM

Processing contributions to IAM

This is a summary of the steps needed to accept a contribution in IAM, as required by the Eclipse IP process.

You should read the detailed explanation (TODO: link).

  • Committers can commit :-).
  • Non-committers (contributors) need to attach the contributions to a bugzilla.

In any case, contributors must answer the following questions (provided for cut&paste in bugzilla, derived from the IP poster):

We need acknowledgment that the provided patches:

  • Do not contain cryptography
  • Are developed from scratch (does not contain IP from others)
  • Are 100% EPL

This is for all content, including XMLs, DTDs, iamges...

Small contribution

If it is small (<250 lines) it can be processed by a committer who reviews it and accepts the contribution. The applied patch/code is then flagged as iplog+ (in the attachment properties).

The Contributor's Name should be listed immediately below the Default Eclipse Copyright and License Notice as a contributor in the header of the files.

Large contribution

If it is larger than 250 lines, it needs to go through IP review. A committer must explicitly request a review:

  1. Review the contribution (usual checks + all the files have the EPL header + contributor name added to the header)
  2. Log in to the portal (http://portal.eclipse.org). Both your committer login and bugzilla login will work.
  3. Use the provided link to open a CQ
  4. Attach the source code to the CQ (no zips, jars...)
  5. A member of the eclipse EMO will review the zip and check that all the obvious things are ok.
  6. A member of the eclipse legal team will do a preliminary review of the code and grant `checkintocvs` flag (as long as we are conforming to the parallel IP process).
  7. The contribution can be included in subversion
  8. The eclipse legal team will do the full review of the code
  9. Once the full review is complete, a release of the project can be made (i.e. no release can happen if the code has only preliminary review).

During the process, we must pay attention to the issues in case there is any question or problem that needs to be addressed.

Did it work?

If everything is done properly, both small and large contributions will show on the automated IP log: