Contributor Agreement - Revision history

Jive at 19:38, 29 October 2007

2007-10-29T19:38:11Z

Jive at 19:37, 29 October 2007

2007-10-29T19:37:00Z

Arnulf at 08:35, 12 September 2006

2006-09-12T08:35:59Z

Arnulf at 12:18, 1 September 2006

2006-09-01T12:18:09Z

Neteler: Category:Incubation

2006-08-21T12:06:27Z

Category:Incubation

Wiki-Rich steele: forgot some clarifying words...

2006-03-07T01:24:59Z

forgot some clarifying words...

Wiki-Rich steele at 01:10, 7 March 2006

2006-03-07T01:10:45Z

Wiki-Rich steele at 07:05, 2 March 2006

2006-03-02T07:05:52Z

Wiki-Rich steele at 00:24, 2 March 2006

2006-03-02T00:24:10Z

Wiki-Rich steele at 23:49, 22 February 2006

2006-02-22T23:49:26Z

@@ Line 1: / Line 1: @@
-''The OSGeo Contributor License Agreement was proposed early in the foundation history, during review it was decided that a contributor agreement is not required. This page is to be considered an example only; project wishing to set up a contributor agreement for their own use may use it as a starting point. Please review the agreement, the FAQ below and comment''
+''The OSGeo Contributor License Agreement was proposed early in the foundation history, during review it was decided that a contributor agreement is *not required*. Please review the agreement, the FAQ below and comment''
-Agreement Forms:
+Example Agreement Forms:
 * Proposed Form of [[Individual Contributor License Agreement (CLA)]]
 * Proposed Form of [[Corporate Contributor License Agreement (CCLA)]]
 ----

← Older revision		Revision as of 19:37, 29 October 2007
Line 1:		Line 1:
−	''The OSGeo Contributor License Agreement is in the review ~~stage and has~~ not ~~been approved formally~~. Please review the agreement, the FAQ below and comment''	+	''The OSGeo Contributor License Agreement was proposed early in the foundation history, during review it was decided that a contributor agreement is not required. This page is to be considered an example only; project wishing to set up a contributor agreement for their own use may use it as a starting point. Please review the agreement, the FAQ below and comment''

	Agreement Forms:		Agreement Forms:

← Older revision		Revision as of 08:35, 12 September 2006
Line 1:		Line 1:
−	''The OSGeo Contributor License Agreement is in the review stage and has ~~noppt~~ been approved formally. Please review the agreement, the FAQ below and comment''	+	''The OSGeo Contributor License Agreement is in the review stage and has not been approved formally. Please review the agreement, the FAQ below and comment''

	Agreement Forms:		Agreement Forms:

← Older revision		Revision as of 12:18, 1 September 2006
Line 1:		Line 1:
−	The OSGeo Contributor License Agreement is in the review stage. Please review the agreement ~~and~~ the FAQ below.	+	''The OSGeo Contributor License Agreement is in the review stage and has noppt been approved formally. Please review the agreement, the FAQ below and comment''

	Agreement Forms:		Agreement Forms:

← Older revision		Revision as of 12:06, 21 August 2006
Line 43:		Line 43:
	; Wow, this is confusing. Where can I learn more about this stuff?		; Wow, this is confusing. Where can I learn more about this stuff?
	: Larry Rosen, the former General Counsel of the OSI, has written an excellent overview book on open source licensing that addresses many of the issues raised by the CLA. In the spirit of open source, the [http://rosenlaw.com/oslbook.htm online version of the book] is available at no charge under the Academic Free License.		: Larry Rosen, the former General Counsel of the OSI, has written an excellent overview book on open source licensing that addresses many of the issues raised by the CLA. In the spirit of open source, the [http://rosenlaw.com/oslbook.htm online version of the book] is available at no charge under the Academic Free License.
		+
		+	[[Category:Incubation]]

@@ Line 39: / Line 39: @@
 ; What if I want to commit a patch or other code sent to me by someone else?  Do they have to sign a CLA too?
-: It depends.  All people with commit access to the code repository ("committers") should have a CLA on file.  A small patch sent by a non-committer that fixes a bug and only impacts a few lines of code can be accepted without a CLA and added to the code repository by a committer.  However, more substantial additions of code, particularly anything that adds new functionality, should not be committed without first obtaining a CLA from the author.  Whether a CLA is a requirement involves some judgment by the committer, with guidance from the PSC as appropriate.  Code provenance and chain of title is important, so in general one should err on the side of obtaining a CLA where there is doubt.
+: It depends.  All people with commit access to the code repository ("committers") should have a CLA on file.  A small patch sent by a non-committer that fixes a bug and only impacts a few lines of code can be accepted without a CLA and added to the code repository by a committer.  However, more substantial additions of code, particularly anything that adds new functionality, should not be committed without first obtaining a CLA from the author.  Whether a CLA is a requirement involves some judgment by the committer, with guidance from the PSC as appropriate.  Code provenance and chain of title is important to protect both you and the foundation, so in general one should err on the side of obtaining a CLA where there is doubt.
 ; Wow, this is confusing.  Where can I learn more about this stuff?
 : Larry Rosen, the former General Counsel of the OSI, has written an excellent overview book on open source licensing that addresses many of the issues raised by the CLA.  In the spirit of open source, the [http://rosenlaw.com/oslbook.htm online version of the book] is available at no charge under the Academic Free License.

@@ Line 37: / Line 37: @@
 ; Will I have to sign a CLA every time I contribute code?
 : No, the CLA covers all of your contributions beginning on the date you sign it.  It also applies to all contributions made to any project managed by OSGeo, so there is no need to execute multiple CLAs for different projects.  However, if you have had your employer sign a Corporate CLA and you later change jobs, you will need to consider whether your new employer should also sign a Corporate CLA.
 ; Wow, this is confusing.  Where can I learn more about this stuff?
 : Larry Rosen, the former General Counsel of the OSI, has written an excellent overview book on open source licensing that addresses many of the issues raised by the CLA.  In the spirit of open source, the [http://rosenlaw.com/oslbook.htm online version of the book] is available at no charge under the Academic Free License.

← Older revision		Revision as of 00:24, 2 March 2006
Line 1:		Line 1:
		+	Note: [[User:Rich_steele]] is preparing a brief explanation/FAQ for the contributor agreement. Stay tuned...
		+
		+	----
		+
	* Proposed Form of [[Individual Contributor License Agreement (CLA)]]		* Proposed Form of [[Individual Contributor License Agreement (CLA)]]
	* Proposed Form of [[Corporate Contributor License Agreement (CCLA)]]		* Proposed Form of [[Corporate Contributor License Agreement (CCLA)]]

← Older revision		Revision as of 23:49, 22 February 2006
Line 1:		Line 1:
−	~~under development by~~ [[~~User:Rich steele \| Rich~~]]	+	* Proposed Form of [[Individual Contributor License Agreement (CLA)]]
		+	* Proposed Form of [[Corporate Contributor License Agreement (CCLA)]]