Difference between revisions of "CLA"

From Eclipsepedia

Jump to: navigation, search
Line 6: Line 6:
  
 
*[[CLA/Implementation Requirements|CLA Implementation Requirements]]
 
*[[CLA/Implementation Requirements|CLA Implementation Requirements]]
 +
* [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&list_id=5143644&short_desc=%5BCLA%5D&short_desc_type=substring CLA Bugs]
 +
** Overhaul our contribution recordkeeping to implement CLAs and signed-off-by {{Bug|401236}}
 +
** Text of the Eclipse Foundation CLA {{Bug|401349}}
 +
** Add Support for CLAs in Gerrit {{Bug|401239}}
 +
** Investigate adding decorators in Bugzilla to indicate whether someone has a CLA on file {{Bug|401549}}
 +
** Implement a git trigger to ensure that all contributions have a CLA on file for the author {{Bug|401240}}
 +
** Automate the process of creating a CLA {{Bug|401238}}
 +
** Create custom schema to contain CLA info {{Bug|401458}}
  
 
[[Category:CLA]]
 
[[Category:CLA]]

Revision as of 10:46, 17 April 2013

The Eclipse Foundation is implementing Contributor License Agreements (CLA) to improve its intellectual property (IP) management and workflow. In part, CLAs are a portion of the work required to implement signed-off-by for all contributions coming to Eclipse via Git or Gerrit.

The desire is to completely automate the workflows associated with CLAs in order to significantly reduce the effort required by contributors and committers to provide and accept contributions to Eclipse projects.

Links