@@ -15,50 +15,68 @@ have to be granted separately.
15
15
If you'd like to apply for one of these roles, please see the main [ Community
16
16
Team] [ communityteam ] page.
17
17
18
+
18
19
## Project Contributor
19
- ### Who should apply:
20
+
21
+ ** Who should apply:**
22
+
20
23
If you’ve contributed to a CC project, you should apply for this role.
21
24
22
- ### What does this role give you?
25
+ ** What does this role give you?**
26
+
23
27
- You’ll receive previews of upcoming changes to the Community Team program.
24
- - You’ll be listed as [ a member of the Community Team on CC Open Source] ( /community/community-team/members/ ) .
28
+ - You’ll be listed as [ a member of the Community Team on CC Open
29
+ Source] ( /community/community-team/members/ ) .
30
+
31
+ ** How can you engage with the community?**
25
32
26
- ### How can you engage with the community?
27
33
You can use the following channels to engage with the community:
28
34
- [ Read access] ( /community/community-team/engagement-channels/#read-access ) on
29
35
the relevant repos on GitHub
30
36
- Invitation to our Slack channels
31
- * [ Newbie
37
+ - [ Newbie
32
38
channels] ( /community/community-team/engagement-channels/#newbie-channels )
33
- * [ UX design
39
+ - [ UX design
34
40
channels] ( /community/community-team/engagement-channels/#ux-design-channel )
35
- * [ Community Team
41
+ - [ Community Team
36
42
channel] ( /community/community-team/engagement-channels/#community-team-channel )
37
43
- Invitation to our
38
44
[ meetings] ( /community/community-team/engagement-channels/#meetings )
39
45
- Membership in the [ Community Team mailing
40
46
list] ( /community/community-team/engagement-channels/#community-team-group )
41
47
42
- ### Guidelines for Project Contributors
48
+ ** Guidelines for Project Contributors**
49
+
43
50
If you’ve been accepted as a Project Contributor, you are encouraged to:
44
51
- keep contributing to the project as and when you can!
45
52
- participate in discussions in Slack or via email.
46
- - contribute in other ways if you'd like, like [ helping out newbie developers or voting on our tweets] ( /community/community-team/community-building-roles/ ) .
53
+ - contribute in other ways if you'd like, like [ helping out newbie developers
54
+ or voting on our
55
+ tweets] ( /community/community-team/community-building-roles/ ) .
56
+
47
57
48
58
## Project Collaborator
49
- ### Who should apply:
50
- 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.
51
59
52
- ### What does this role give you?
60
+ ** Who should apply:**
61
+
62
+ If you’ve made a few significant contributions to the project (added new
63
+ features, for example) and know the project’s overall codebase pretty well, you
64
+ should apply.
65
+
66
+ ** What does this role give you?**
67
+
53
68
- Everything a Project Contributor gets.
54
69
- Creative Commons staff will write you a letter of recommendation on request.
55
70
56
- ### How can you engage with the community?
57
- In addition to the channels afforded to a Project Contributor, you can use the following channels to engage with the community:
71
+ ** How can you engage with the community?**
72
+
73
+ In addition to the channels afforded to a Project Contributor, you can use the
74
+ following channels to engage with the community:
58
75
- [ Triage access] ( /community/community-team/engagement-channels/#triage-access )
59
76
on the relevant repos on GitHub
60
77
61
- ### Guidelines for Project Collaborators
78
+ ** Guidelines for Project Collaborators**
79
+
62
80
If you’ve been accepted as a Project Collaborator, you are encouraged to:
63
81
- do everything a Project Contributor does.
64
82
- review and triage new issues.
@@ -75,54 +93,65 @@ If you’ve been accepted as a Project Collaborator, you are encouraged to:
75
93
** Note:** The role of Project Member was deprecated in July 2020 and all
76
94
members were redesignated as collaborators.
77
95
96
+
78
97
## Project Core Committer
79
98
80
- ### Who should apply:
99
+ ** Who should apply:**
100
+
81
101
If you’ve made many significant contributions to the project, know the codebase
82
102
really well, and are interested in active maintenance of the project, you
83
103
should apply.
84
104
85
- ### What does this role give you?
105
+ ** What does this role give you?**
86
106
87
107
- Everything a Project Collaborator gets.
88
- - You’ll be eligible to mentor GSoC, GSoD and Outreachy interns (and similar) for Creative Commons.
89
- - You'll receive CC swag.
108
+ - You’ll be eligible to lead projects for the GSoC, GSoD, and Outreachy work
109
+ programs (and similar) for Creative Commons.
110
+
111
+ ** How can you engage with the community?**
90
112
91
- ### How can you engage with the community?
92
113
In addition to the channels afforded to a Project Collaborator, you can use the
93
114
following channels to engage with the community:
94
115
- [ Write access] ( /community/community-team/engagement-channels/#write-access )
95
116
on the relevant repos on GitHub
96
117
97
- ### Guidelines for Project Core Committers
118
+ ** Guidelines for Project Core Committers**
119
+
98
120
If you’ve been accepted as a Project Core Committer, you are encouraged to:
99
121
- do everything a Project Collaborator does.
100
122
- merge PRs that you are confident work well and fit the project guidelines.
101
123
- If you have any doubts, please check with project maintainers first!
102
124
- proactively ask about mentorship opportunities if that interests you.
103
125
126
+
104
127
## Project Maintainer
105
128
106
- ### Who should apply:
129
+ ** Who should apply:**
130
+
107
131
If you’re a Core Committer already and you’re interested in taking on
108
132
maintainer responsibilities, you should apply. Please note that this role comes
109
133
with a lot of responsibilities!
110
134
111
- ### What does this role give you?
135
+ ** What does this role give you?**
136
+
112
137
Everything a Project Core Committer gets.
113
138
114
- ### How can you engage with the community?
139
+ ** How can you engage with the community?**
140
+
115
141
In addition to the channels afforded to a Project Core Committer, you can use
116
142
the following channels to engage with the community:
117
143
- [ Maintain
118
144
access] ( /community/community-team/engagement-channels/#maintain-access ) on
119
145
the relevant repos on GitHub
120
146
121
- ### Guidelines for Project Maintainers
147
+ ** Guidelines for Project Maintainers**
148
+
122
149
Being a Project Maintainer comes with a larger set of responsibilities and
123
150
guidelines, documented below:
124
151
152
+
125
153
### Responsibilities
154
+
126
155
As a Project Maintainer, your responsibilities are as follows:
127
156
128
157
- ** Review pull requests (PRs):** You are expected to review incoming pull
@@ -148,7 +177,9 @@ Team directly and let them know the status of their application.
148
177
provide them with the link to the Community Team page on the CC Open Source
149
178
site, and encourage them to apply.
150
179
180
+
151
181
### Reviewing Community Team Applications
182
+
152
183
Applications for Community Team roles will be sent to you individually by the
153
184
Open Source Community Coordinator (OSCC). The OSCC has ensured that the bare
154
185
requirements for the position are met. If bare requirements are not met, you
@@ -176,7 +207,9 @@ No matter the decision, you should do the following things:
176
207
days or less from time of application to time of decision, but this is
177
208
somewhat flexible.
178
209
210
+
179
211
### Additional Notes
212
+
180
213
All Community Team work is done on a volunteer basis. Team members may pick up
181
214
tasks and help out here and there if they would like, but they should not be
182
215
expected to use all of their privileges all the time.
0 commit comments