You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/community/community-teams/contents.lr
+10-2
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ Privileges and access will be granted per-repository. For example, if you are ap
61
61
|**Project Contributor**<br>You should apply for this role if you are interested in dipping your toe into Community Teams. | <li>Invitation to private community contributors Slack channel.</li><li>Addition to Community Team page on CC Open Source.</li> | 3 contributions.<br><br>1 merged pull request or “Great Contribution” to the project you’re applying for. |
62
62
|**Project Member**<br>If you've given Community Teams a shot and are ready to take the next step, this role is for you! As a Project Member, you will gain experience with issue triage and real-world open source governance workflows. | <li>All <b>Project Contributor</b> privileges.</li><li>Addition to creativecommons GitHub organization with Triage access to the GitHub repo associated with the project.</li><ulstyle="list-style-type: circle"><li>This will allow you to update labels on issues, etc.</li></ul> | 15 contributions with at least 4 pull requests* submitted to the project you’re applying for.<br><br>3 “Great” Contributions |
63
63
|**Project Collaborator**<br>You should apply for this role if you are interested in being deeply involved with a project, and engaging closely with CC Staff, Project Maintainers, and Core Committers. This role also gives you the opportunity to mentor others through GSoC and Outreachy. | <li>All <b>Project Member</b> privileges.</li><li>Addition to project’s CODEOWNERs file.</li><ulstyle="list-style-type: circle"><li>This will allow your PR reviews to block merge.</li><li>This will auto assign you PRs to review.</li></ul><li>Eligibility to mentor interns for programs like GSoC and Outreachy for Creative Commons.</li><li>Invitation to some of CC’s internal meetings and Slack channels.</li><li>Letter of recommendation from Creative Commons available on request.</li> | 35 contributions with at least 8 pull requests* submitted to the project you’re applying for.<br><br>5 “Great” Contributions |
64
-
|**Project Core Committer**<br>| <li>All <b>Project Collaborator</b> privileges.</li><li>Write access to the project's GitHub repo.</li><ulstyle="list-style-type: circle"><li>This will allow you to merge PRs.</li></ul> | N/A, Maintainers will invite standout contributors. |
64
+
|**Project Core Committer**| <li>All <b>Project Collaborator</b> privileges.</li><li>Write access to the project's GitHub repo.</li><ulstyle="list-style-type: circle"><li>This will allow you to merge PRs.</li></ul> | N/A, Maintainers will invite standout contributors. |
65
65
66
66
### Community Roles
67
67
@@ -71,7 +71,7 @@ These roles are not project based and are for folks interested in helping grow C
|**Community Contributor**<br>If you'd like to try out engaging with the CC community on a deeper level, but aren't familiar with the technical side of things, you might like this role! | <li>Invitation to private community contributors Slack channel.</li><li>Addition to Community Team page on CC Open Source.</li> | 3 contributions.<br><br>1 published tweet to the CC Open Source Twitter account based on an idea submitted by you or “Great Contribution” on any project.<br><br>General community interaction. |
73
73
|**Community Collaborator**<br>So you've tried out being a Community Contributor, want to engage more directly with the CC com, and more deeply with the community itself. This role is for you! | <li>All <b>Community Contributor</b> privileges.</li><li>Comment-only access to the Open Source Community project on Asana, with the option to pick up tasks if desired.</li> | 15 contributions.<br><br>At least five people helped on Slack or the mailing list. |
74
-
|**Community Maintainer**<br>| <li>All <b>Community Collaborator</b> privileges.</li><li>Manager permission on CC’s developer mailing list.</li><li>Access to tweet directly from CC Open Source account.</li><li>Letter of recommendation from Creative Commons available on request.</li> | N/A, Maintainers will watch and select standout contributors |
74
+
|**Community Maintainer**| <li>All <b>Community Collaborator</b> privileges.</li><li>Manager permission on CC’s developer mailing list.</li><li>Access to tweet directly from CC Open Source account.</li><li>Letter of recommendation from Creative Commons available on request.</li> | N/A, Maintainers will watch and select standout contributors |
75
75
76
76
How to Apply
77
77
------------
@@ -98,6 +98,14 @@ Great contributions are those that are of a high level of quality such that a ma
98
98
99
99
Your code does not necessarily need to be merged to count as a "Great Contribution".
<dt>You can nominate three of your contributions made before April 28, 2020 to be retroactively recognized as "Great Contributions" until May 13, 2020.</dt>
103
+
<dd>To take advantage of this limited-time opportunity, please submit your contributions through <ahref="https://docs.google.com/forms/d/e/1FAIpQLSe7-emB8BAnheVT1_oJQshJ3WzwIfA9PVM1sj9ouTTzTAMFwA/viewform?usp=sf_link">this Google Form</a>.</dd>
104
+
<dd>• Decisions on whether or not to recognize a contribution as “Great” are final, please do not message maintainers to inquire about the status of your submission, or to appeal a decision.</dd>
105
+
<dd>• We are only taking a maximum of three contributions per person, be sure to submit the ones that you think are the strongest!</dd>
106
+
<dd>• Please only submit your own contributions, not someone else's, and please submit only the link to the contribution.</dd>
107
+
</dl>
108
+
101
109
<b>What counts as a required pull request?</b>
102
110
103
111
If you are applying for a project based role, required pull requests must be made to the repository that you are applying for. Required pull requests do not need to be merged, they could be closed or awaiting review.
0 commit comments