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
*[Community Team channel](/community/community-team/engagement-channels/#community-team-channel)
29
-
*[Community Team mailing list](/community/community-team/engagement-channels/#community-team-group)
30
+
* Invitation to our [meetings](/community/community-team/engagement-channels/#meetings)
31
+
* Membership in the [Community Team mailing list](/community/community-team/engagement-channels/#community-team-group)
30
32
31
33
**Guidelines for Community Contributors**
32
34
If you’ve been accepted as a Community Contributor, you are encouraged to:
33
35
* keep helping people in the CC open source community!
34
-
*respond to people on Slack.
35
-
*respond to questions or issues on GitHub.
36
-
*respond to people on CC's mailing lists.
36
+
*Respond to people on Slack.
37
+
*Respond to questions or issues on GitHub.
38
+
*Respond to people on CC's mailing lists.
37
39
* participate in discussions in Slack or via email.
38
40
* contribute in other ways if you’d like, like [writing code or reviewing pull requests](/community/community-team/project-roles/).
39
41
40
42
## Community Collaborator
41
-
**Who should apply:** If you’ve helped a few people in the CC open source community and you’d like to do more to help grow the community, you should apply for this role!
43
+
**Who should apply:**
44
+
If you’ve helped a few people in the CC open source community and you’d like to do more to help grow the community, you should apply for this role!
42
45
43
-
**What does this role give you?**
46
+
**What does this role give you?**
44
47
* Everything a Community Contributor gets.
45
-
* Comment-only access to the Open Source Community project on Asana.
46
-
* You’ll see our future plans for the open source community and have the opportunity to participate in them.
47
48
48
-
**How can you engage with the community?**
49
+
**How can you engage with the community?**
49
50
In addition to the channels afforded to a Community Contributor, you can use the following channels to engage with the community:
50
-
*[Suggest access](/community/community-team/engagement-channels/#suggest-access) on
If you’ve been accepted as a Community Collaborator, you are encouraged to:
59
56
* do everything a Community Contributor does.
60
-
* participate in the Asana project and do some tasks on there.
61
57
* suggest Tweet ideas for the [CC Open Source Twitter account](https://twitter.com/cc_opensource).
62
58
63
59
## Community Maintainer
64
-
**Who should apply:** If you’re a Community Collaborator who has done some meatier community building tasks and wants more responsibility, you should apply for this role. Please note that this role comes with a lot of responsibilities!
60
+
**Who should apply:**
61
+
If you’re a Community Collaborator who has done some meatier community building tasks and wants more responsibility, you should apply for this role. Please note that this role comes with a lot of responsibilities!
65
62
66
-
**What does this role give you?**
63
+
**What does this role give you?**
67
64
* Everything a Community Collaborator gets.
68
-
* Full access to the Open Source Community project on Asana.
69
-
* You’ll be able to add new tasks.
70
65
* Manager permission on CC’s developer mailing list.
71
66
* You’ll be able to approve new requests for people to join and moderate the list.
72
67
* Creative Commons staff will write you a letter of recommendation on request.
73
68
* You'll receive CC swag.
74
69
75
-
**How can you engage with the community?**
70
+
**How can you engage with the community?**
76
71
In addition to the channels afforded to a Community Collaborator, you can use the following channels to engage with the community:
77
72
*[Compose access](/community/community-team/engagement-channels/#compose-access) on
*[Community Team channel](/community/community-team/engagement-channels/#community-team-channel)
30
+
* Invitation to our [meetings](/community/community-team/engagement-channels/#meetings)
31
+
* Membership in the [Community Team mailing list](/community/community-team/engagement-channels/#community-team-group)
28
32
29
33
**Guidelines for Project Contributors**
30
34
If you’ve been accepted as a Project Contributor, you are encouraged to:
@@ -33,46 +37,38 @@ If you’ve been accepted as a Project Contributor, you are encouraged to:
33
37
* contribute in other ways if you'd like, like [helping out newbie developers or voting on our tweets](/community/community-team/community-building-roles/).
34
38
35
39
## Project Collaborator
36
-
**Who should apply:** If you’ve made a few significant contributions to the project (added new features, for example) and know the project’s overall codebase pretty well, you should apply.
40
+
**Who should apply:**
41
+
If you’ve made a few significant contributions to the project (added new features, for example) and know the project’s overall codebase pretty well, you should apply.
37
42
38
-
**What does this role give you?**
43
+
**What does this role give you?**
39
44
* Everything a Project Contributor gets.
40
45
* Creative Commons staff will write you a letter of recommendation on request.
41
46
42
47
**How can you engage with the community?**
43
48
In addition to the channels afforded to a Project Contributor, you can use the following channels to engage with the community:
If you’ve been accepted as a Project Collaborator, you are encouraged to:
59
54
* do everything a Project Contributor does.
60
55
* review and triage new issues.
61
-
*ask the issue author for more details if appropriate.
62
-
*check with the project maintainers if the issue makes sense.
63
-
*update the labels on the issue appropriately once you have all the information you need (e.g. remove “awaiting triage” label).
56
+
*Ask the issue author for more details if appropriate.
57
+
*Check with the project maintainers if the issue makes sense.
58
+
*Update the labels on the issue appropriately once you have all the information you need (e.g. remove “awaiting triage” label).
64
59
* review assigned pull requests to unblock merges.
65
60
* participate in discussions in the new meetings and channels you’ve been added to.
66
61
* identify promising contributors to the project and invite them to join the Community Team.
67
62
68
63
**Note:** The role of Project Member was deprecated in July 2020 and all members were redesignated as collaborators.
69
64
70
65
## Project Core Committer
71
-
**Who should apply:** If you’ve made many significant contributions to the project, know the codebase really well, and are interested in active maintenance of the project, you should apply.
66
+
**Who should apply:**
67
+
If you’ve made many significant contributions to the project, know the codebase really well, and are interested in active maintenance of the project, you should apply.
72
68
73
-
**What does this role give you?**
69
+
**What does this role give you?**
74
70
* Everything a Project Collaborator gets.
75
-
* You’ll be eligible to mentor GSoC and Outreachy interns (and similar) for Creative Commons.
71
+
* You’ll be eligible to mentor GSoC, GSoD and Outreachy interns (and similar) for Creative Commons.
76
72
* You'll receive CC swag.
77
73
78
74
**How can you engage with the community?**
@@ -86,15 +82,13 @@ If you’ve been accepted as a Project Core Committer, you are encouraged to:
86
82
* merge PRs that you are confident work well and fit the project guidelines.
87
83
* if you have any doubts, please check with project maintainers first!
88
84
* proactively ask about mentorship opportunities if that interests you.
89
-
* recognize other contributions with “Great Contribution” labels
90
-
* more details are available in the "Great Contribution" section in the Project Maintainer guidelines below.
91
85
92
86
## Project Maintainer
93
-
**Who should apply:** If you’re a Core Committer already and you’re interested in taking on maintainer responsibilities, you should apply. Please note that this role comes with a lot of responsibilities!
87
+
**Who should apply:**
88
+
If you’re a Core Committer already and you’re interested in taking on maintainer responsibilities, you should apply. Please note that this role comes with a lot of responsibilities!
94
89
95
-
**What does this role give you?**
90
+
**What does this role give you?**
96
91
* Everything a Project Core Committer gets.
97
-
* This will allow you to manage some repository settings.
98
92
99
93
**How can you engage with the community?**
100
94
In addition to the channels afforded to a Project Core Committer, you can use the following channels to engage with the community:
@@ -107,32 +101,14 @@ Being a Project Maintainer comes with a larger set of responsibilities and guide
107
101
### Responsibilities
108
102
As a Project Maintainer, your responsibilities are as follows:
109
103
110
-
***Review pull requests (PRs):** You are expected to review incoming pull requests regularly (we aim to review all pull requests within [within three business days][pullrequestguidelines]).
111
-
***Recognize work as "Great Contribution":**You are expected to pay attention to contributions to your repositories, and apply “Great Contribution” labels as needed. For more information about this, see the “Great Contributions” section below.
104
+
***Review pull requests (PRs):** You are expected to review incoming pull requests regularly (we aim to review all pull requests within [within three business days](/contributing-code/pr-guidelines)).
112
105
***Decide on Community Team applications:** You are expected to make the final decision on Community Team applications for your project.
113
106
***Communicate with the applicant and the Open Source Community Coordinator (OSCC) promptly:** You are expected to reach out to applicants for Community Team directly and let them know the status of their application.
114
107
* We want to get back to applicants within seven business days of application, if possible. If this is not possible, you should reach out to the applicant just letting them know that it’s taking a little longer than usual (could be due to internal discussion taking a while, other things taking precedent, etc.), and that we’re working on it.
115
108
* You are expected to communicate with the OSCC promptly (within three business days) when they reach out to you about a new Community Team application or other related matter.
116
109
* You should also notify the OSCC of your decision about the Community Team application.
117
110
***Let contributors know about Community Team:** If you notice a strong contributor, you should notify them of the existence of Community Team, provide them with the link to the Community Team page on the CC Open Source site, and encourage them to apply.
“Great Contributions” are evaluated subjectively. If you notice that a contribution was of particularly high quality, you should mark it as a “Great Contribution”.
125
-
126
-
Guidelines for what to mark as a “Great Contribution”:
127
-
* A substantial PR (e.g. not fixing two links in a README; work should reasonably take an hour or more, assuming they’re not familiar with the project)
128
-
* Shows hard work
129
-
* Responsive to feedback
130
-
131
-
How to label “Great Contributions”:
132
-
* Assign the issue or PR to whoever made the great contribution.
133
-
* Apply the “Great Contribution” label to the issue or PR.
134
-
* Notify whoever made the great contribution that it has been recognized as such.
135
-
136
112
### Reviewing Community Team Applications
137
113
Applications for Community Team roles will be sent to you individually by the Open Source Community Coordinator (OSCC). The OSCC has ensured that the bare requirements for the position are met. If bare requirements are not met, you will be notified how so when you receive the application from the OSCC.
0 commit comments