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
+15-15
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ Joining the community team involves three steps:
19
19
- You'll gain practical, real world, open source experience.
20
20
- You'll build both technical and soft skills.
21
21
- You'll work closely with and be mentored by CC's experienced software engineers and community contributors.
22
-
- You'll build your resume.
22
+
- You'll build your resume.
23
23
- You'll be given "priority" in internship applications (not an automatic bump, but if the applicant is known for good quality, that's a big advantage)
24
24
- You'll advance the Creative Commons mission
25
25
- You'll engage with CC's global Free/Libre and Open Source (FLOSS) community!
@@ -55,22 +55,22 @@ These roles are specific to a single CC project (usually limited to a single git
55
55
56
56
Privileges and access will be granted per-repository. For example, if you are applying for a role on the `cccatalog-frontend` repository, you would want to concentrate your contributions on `cccatalog-frontend`.
|**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 |
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. |
58
+
| Name | Privileges | Requirements |
59
+
|----|-----------|-------------|
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 |
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. |
64
64
65
65
### Community Roles
66
66
67
67
These roles are not project based and are for folks interested in helping grow CC's open source community by ensuring all contributors have a good experience and spreading the word about CC's projects.
|**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 |
69
+
| Name | Privileges | Requirements |
70
+
|----|-----------|-------------|
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 |
74
74
75
75
How to Apply
76
76
------------
@@ -120,7 +120,7 @@ Here are a few criteria that are especially important when we evaluate whether w
120
120
121
121
1. Conduct and Communication
122
122
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.
123
-
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.
123
+
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.
124
124
<br/>
125
125
2. Quality of Contributions
126
126
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.
@@ -140,9 +140,9 @@ Privilege & Role De-escalation
140
140
1. Breach of code of conduct.
141
141
2. Inactivity for a period of six months or longer from the time of last contribution.
142
142
3. Dramatic drops in quality of work.
143
-
4. Maintainer discretion.
143
+
4. Maintainer discretion.
144
144
<br/>
145
145
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:
146
146
1. Revocation of some privileges.
147
147
2. Revocation of all privileges.
148
-
3. Notice that privileges may be revoked due to inactivity.
148
+
3. Notice that privileges may be revoked due to inactivity.
0 commit comments