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
+14-16
Original file line number
Diff line number
Diff line change
@@ -30,12 +30,12 @@ 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 OK! 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
-
- 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.
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.
37
37
-[Writing Blog Posts](https://opensource.creativecommons.org/community/write-a-blog-post/): Blog about your work and contributions to CC projects or about your own CC-related projects.
38
-
- This is a great way to document the time spent in the CC community, and gives a good opportunity for introspection.
38
+
- This is a great way to document the time spent in the CC community, and gives a good opportunity for introspection.
39
39
- Helping Others: Be active and help answer other people's questions in CC open source community forums.
40
40
- Pull Request Review: Review other people's pull requests (see [our pull request guidelines](https://opensource.creativecommons.org/contributing-code/pr-guidelines/)).
41
41
- Tweet Ideas: Submit ideas for tweets from CC's Open Source Twitter account via [this form](https://docs.google.com/forms/d/e/1FAIpQLSebelW-zkpaQb-gRyhHeE-Ux-6c3WtO7pU6CWTbkAoPfDnZYg/viewform?usp=sf_link).
@@ -55,9 +55,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><ul><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><ul><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 Core Committer**| <li>All <b>Project Collaborator</b> privileges.</li><li>Write access to the project's GitHub repo.</li><ul><li>This will allow you to merge PRs.</li></ul> | N/A, Maintainers will invite standout contributors. |
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 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
61
62
62
### Community Roles
63
63
@@ -66,8 +66,8 @@ 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 **Community Contributor** 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 **Community Collaborator** 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 |
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
71
72
72
How to Apply
73
73
------------
@@ -104,9 +104,8 @@ Here are a few criteria that are especially important when we evaluate whether w
104
104
105
105
1. Conduct and Communication
106
106
1. Contributors are expected to follow the CC Open Source [Code of Conduct](https://opensource.creativecommons.org/community/code-of-conduct/). Breaches will seriously damage a contributor's chances of being granted further privileges, and will almost certainly result in a de-escalation of privileges if applicable.
107
-
2. Contributor interaction with maintainers and other contributors should be generally helpful and constructive. Responding to messages and pull request comments quickly (within a couple of days) is also looked upon favorably.
108
-
109
-
107
+
2. Contributor interaction with maintainers and other contributors should be generally helpful and constructive. Responding to messages and pull request comments quickly (within a couple of days) is also looked upon favorably.
108
+
<br/>
110
109
2. Quality of Contributions
111
110
1. Contributors are expected to refrain from trying to meet issue or PR submission requirements by creating duplicate, invalid, or unreasonably small issues/PRs simply to meet requirements.
112
111
2. Consistently low quality code will reflect poorly on contributors. Contributors will receive feedback on their contributions if a maintainer sees the potential for improvement. Demonstrated ability to incorporate feedback over time will reflect favorably.
@@ -121,14 +120,13 @@ Here are a few criteria that are especially important when we evaluate whether w
121
120
Privilege & Role De-escalation
122
121
------------------------------
123
122
124
-
1.Reasons: Roles and/or privileges may be revoked or de-escalated for any time at any reason, but this should be uncommon. De-escalation of privileges may happen for reasons including, but not limited to the following:
123
+
1. Reasons: Roles and/or privileges may be revoked or de-escalated for any time at any reason, but this should be uncommon. De-escalation of privileges may happen for reasons including, but not limited to the following:
125
124
1. Breach of code of conduct.
126
125
2. Inactivity for a period of six months or longer from the time of last contribution.
127
126
3. Dramatic drops in quality of work.
128
-
4. Maintainer discretion.
129
-
130
-
131
-
2. Procedure: Depending on the nature of what is causing the de-escalation, different steps may be taken, and maintainers and/or admins may (or may not) discuss measures to be taken. These measures may include, but are not limited to:
127
+
4. Maintainer discretion.
128
+
<br/>
129
+
2. Procedure: Depending on the nature of what is causing the de-escalation, different steps may be taken, and maintainers and/or admins may (or may not) discuss measures to be taken. These measures may include, but are not limited to:
132
130
1. Revocation of some privileges.
133
131
2. Revocation of all privileges.
134
132
3. Notice that privileges may be revoked due to inactivity.
0 commit comments