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
+26-10
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ How to Contribute
30
30
You can contribute to CC in a variety of ways!
31
31
32
32
-[Code Contribution](https://opensource.creativecommons.org/contributing-code/): Submit a pull request for a CC project.
33
-
- We value the quality of your contributions highly, but if you are new to CC, open source, or even programming as a whole, this is OK! Possibly more important than quality is that you show you can incorporate feedback, and show potential for growth.
33
+
- We value the quality of your contributions highly, but if you are new to CC, open source, or even programming as a whole, this is okay! Possibly more important than quality is that you show you can incorporate feedback, and show potential for growth.
34
34
- Documentation: Improve documentation for a CC project.
35
35
- We want our projects to cover [all four bases of good documentation](https://documentation.divio.com/introduction/): tutorials, how-to guides, reference documentation, and explanations.
36
36
- Issue Reporting: Report bugs or write up feature requests for a CC project.
@@ -46,6 +46,9 @@ Roles
46
46
47
47
**CC's Community Team has a lot of different roles. You can apply for each role upon meeting the requirements!**
48
48
49
+
All of these privileges are granted on a volunteer basis, and there is no obligation to leverage any of them if you don't want to.
50
+
If school, family, work, or otherwise takes precedent, that's okay! For example, assigned pull request reviews: we would like to see your review on that PR, but if you are not able or don't want to complete the review, that's okay!
51
+
49
52
### Project-Based Roles
50
53
51
54
These roles are specific to a single CC project (usually limited to a single git repository). You may have roles on multiple projects, but they will have to be applied for separately. If you're interested in writing code primarily, you'll want to apply to these roles.
@@ -54,9 +57,9 @@ Privileges and access will be granted per-repository. For example, if you are ap
|**Project Contributor**| <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. |
58
-
|**Project Member**| <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 |
59
-
|**Project Collaborator**| <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 |
60
+
|**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. |
61
+
|**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 |
62
+
|**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 |
60
63
|**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. |
61
64
62
65
### Community Roles
@@ -65,37 +68,50 @@ These roles are not project based and are for folks interested in helping grow C
|**Community Contributor**| <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. |
69
-
|**Community Collaborator**| <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. |
70
-
|**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|
71
+
|**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. |
72
+
|**Community Collaborator**<br>So you've tried out being a Community Contributor, want to engage more directly with the CC team 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. |
73
+
|**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 |
71
74
72
75
How to Apply
73
76
------------
74
77
75
78
Please apply via [this Google Form](https://docs.google.com/forms/d/e/1FAIpQLScEQPWt30B_KHGlqtmCKDWcRID7O8k2GUcC4opoVh8pHAe5gQ/viewform?usp=sf_link).
76
79
80
+
We will do our best to review applications in a timely manner, and respond to applicants with a decision within seven business days of submission.
81
+
We know that waiting can be difficult, but please refrain from sending messages to maintainers inquiring about the status of your application. Rest assured that we are working on it!
82
+
77
83
### Frequently Asked Questions
78
84
79
-
<b>What counts as a contribution?</b>
85
+
**What counts as a contribution?**
80
86
81
87
Contributions can be any of the things listed under ["How to Contribute"](https://opensource.creativecommons.org/community/community-teams/#how-to-contribute) above. If you think something should count as a contribution that's not listed above, please put that in your application.
82
88
83
89
Individual repositories may have additional work that counts as a contribution. If this is the case, these additional contributions will be documented in that repository's README.
84
90
85
91
To count as a contribution, Issue submissions and pull request reviews don't have to be in the repository you are targeting, they could be for any CC project. However, the required pull requests must be submitted in the project you are targeting.
86
92
87
-
<b>What is a "Great Contribution"? </b>
93
+
**What is a "Great Contribution"?**
88
94
89
95
Great contributions are those that are of a high level of quality such that a maintainer takes notice. When a maintainer takes notice, they will mark the contribution with the "Great Contribution" label on GitHub. Some examples of things that might make maintainers take notice include (but are not limited to), well-written code, good work on a difficult task, or the quality of the solution as a whole.
90
96
91
97
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>
101
+
<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>
102
+
<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>
103
+
<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>
104
+
<dd>• Please only submit your own contributions, not someone else's, and please submit only the link to the contribution.</dd>
105
+
</dl>
106
+
107
+
**What counts as a required pull request?**
94
108
95
109
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.
96
110
97
111
Pull requests do not have to be code, they can be documentation as well.
98
112
113
+
**If your question is not answered here, please ask us on Slack, or at <ahref="mailto:opensource@creativecommons.org">opensource@creativecommons.org</a>!**
114
+
99
115
### Evaluation Criteria
100
116
101
117
Contributors are only eligible for each role after meeting requirements, the role is not guaranteed. Granting of the role depends on staff and maintainer approval.
0 commit comments