Project Governance/New Contributor and Access Policy - Revision history

Dan Mills: Dan Mills moved page Governance/New Contributor and Access Policy to Project Governance/New Contributor and Access Policy: A concern was raised that "Governance" could be confused to mean CC-wide governance, which is not true (CC has a formal l...

2013-10-03T17:27:45Z

Dan Mills moved page Governance/New Contributor and Access Policy to Project Governance/New Contributor and Access Policy: A concern was raised that "Governance" could be confused to mean CC-wide governance, which is not true (CC has a formal l...

2013-09-23T20:50:27Z

Protected "Governance/New Contributor and Access Policy" (‎[edit=sysop] (indefinite) ‎[move=sysop] (indefinite))

2013-09-23T20:50:11Z

2013-09-06T20:36:21Z

‎Problems With Your Account

2013-09-06T20:31:55Z

2013-09-03T23:28:30Z

‎Contributor Agreement

2013-09-03T23:19:55Z

‎Requesting Access

2013-09-03T23:14:01Z

‎Requesting Access

2013-09-03T23:11:49Z

‎Access Levels

2013-09-03T23:11:26Z

‎Requesting Access

@@ Line 1: / Line 1: @@
 == Introduction ==
@@ Line 85: / Line 83: @@
 If you suspect your account has been compromised, or are having trouble accessing your account, please [https://github.com/creativecommons/governance/issues/new file a new issue] with the "Account problem" label (preferred), or if you are not able to access Github, please send an email to [mailto:admin@creativecommons.org admin@creativecommons.org].
 {{IncludesContentWithLicense|site=www.mozilla.org|page=hacking/committer}}
 {{IncludesContentFrom|site=www.mozilla.org|page=hacking/commit-access-policy}}

← Older revision		Revision as of 20:36, 6 September 2013
Line 86:		Line 86:

	{{IncludesContentWithLicense\|site=www.mozilla.org\|page=hacking/committer}}		{{IncludesContentWithLicense\|site=www.mozilla.org\|page=hacking/committer}}
		+	{{IncludesContentFrom\|site=www.mozilla.org\|page=hacking/commit-access-policy}}

← Older revision		Revision as of 20:31, 6 September 2013
Line 84:		Line 84:

	If you suspect your account has been compromised, or are having trouble accessing your account, please [https://github.com/creativecommons/governance/issues/new file a new issue] with the "Account problem" label (preferred), or if you are not able to access Github, please send an email to [mailto:admin@creativecommons.org admin@creativecommons.org].		If you suspect your account has been compromised, or are having trouble accessing your account, please [https://github.com/creativecommons/governance/issues/new file a new issue] with the "Account problem" label (preferred), or if you are not able to access Github, please send an email to [mailto:admin@creativecommons.org admin@creativecommons.org].
		+
		+	{{IncludesContentWithLicense\|site=www.mozilla.org\|page=hacking/committer}}

@@ Line 60: / Line 60: @@
 == Contributor Agreement ==
-(TBD)
+All contributors must agree to the Contributor Agreement. A copy of the agreement is here (link TBD...). In order to agree, you must:
 == Vouchers ==

@@ Line 49: / Line 49: @@
 # Read this document carefully and decide which level of access you need to apply for.
 # Open a [https://github.com/creativecommons/governance/issues/new new issue] for your request. Add the "Repository Access Request" label and make sure you include:
 #* your name

← Older revision	Revision as of 17:27, 3 October 2013
(No difference)

← Older revision	Revision as of 20:50, 23 September 2013
(No difference)

@@ Line 55: / Line 55: @@
 #* the level of access you are requesting
 #* if you are requesting access to any level 3 repositories, list them
-# If you have not already done so, complete the Contributor Agreement (link to agreement & process TBD).
+# If you have not already done so, complete the Contributor Agreement (see Contributor Agreement section below).
 # Ensure all the required vouchers for the level and repository in question are in the issue (as comments).
 # A CC representative will double-check that the needed info is recorded and, if so, give you the necessary access or next steps.

@@ Line 39: / Line 39: @@
 : This level is generally appropriate for most code and website content, except for legal content (e.g., legal code).
-; Level 3 (specific repositories)
+; Level 3 (sensitive repositories)
 : Repositories marked "level 3" require two vouchers, as in level 2, but one of them must be of the owner of the level 3 repository the contributor wishes to contribute to. Unlike other levels, gaining level 3 access does not grant access to all level 3 repositories, but rather only the level 3 repository approved by the module owner. Gaining access to additional level 3 repositories requires only one voucher from the responsible module owner.