Jump to: navigation, search

Difference between revisions of "Development Resources/IP Due Diligence for Git and Gerrit"

Line 3: Line 3:
 
Git provides makes it easy to wrap and indefinitely persist contributions along with metadata. Specifically, contributions delivered via Git are packed into commit records that include the identity of the contributor, dates, comments, etc.
 
Git provides makes it easy to wrap and indefinitely persist contributions along with metadata. Specifically, contributions delivered via Git are packed into commit records that include the identity of the contributor, dates, comments, etc.
  
Contributor starts here:
+
Project information pages include a block that looks something like this:
  
 
[[Image:Contribute section.png]]
 
[[Image:Contribute section.png]]
 +
 +
The very first paragraph contains a link to this page. Project-specific "how to contribute" pages provide a similar link.
 +
 +
==The Contribution==
 +
 +
The contribution must have the author field set to the contributor's credentials.
 +
 +
Further, the contribution my be "signed-off-by" the contributor using identical credentials; e.g.
 +
Signed-off-by: Wayne Beaton <wayne@eclipse.org>
  
 
By signing off on a contribution, you assert that:
 
By signing off on a contribution, you assert that:

Revision as of 21:37, 30 October 2012

Warning2.png
This is a work-in-progress that hasn't been implemented yet. The Eclipse IP Due Diligence Process poster is the authority with regard to how IP contributions must be handled.


Git provides makes it easy to wrap and indefinitely persist contributions along with metadata. Specifically, contributions delivered via Git are packed into commit records that include the identity of the contributor, dates, comments, etc.

Project information pages include a block that looks something like this:

Contribute section.png

The very first paragraph contains a link to this page. Project-specific "how to contribute" pages provide a similar link.

The Contribution

The contribution must have the author field set to the contributor's credentials.

Further, the contribution my be "signed-off-by" the contributor using identical credentials; e.g.

Signed-off-by: Wayne Beaton <wayne@eclipse.org>

By signing off on a contribution, you assert that:

  1. I have authored 100% of the content I'm contributing
  2. I have the rights to donate the content to Eclipse
  3. I contribute the content under the EPL