Skip to content

Commit 4f32e55

Browse files
committed
Merge branch 'work-programs-reorg-2' into gsoc2022-unaccepted
2 parents 55f8db3 + 35a8831 commit 4f32e55

File tree

1 file changed

+58
-25
lines changed
  • content/community/community-team/project-roles

1 file changed

+58
-25
lines changed

content/community/community-team/project-roles/contents.lr

+58-25
Original file line numberDiff line numberDiff line change
@@ -15,50 +15,68 @@ have to be granted separately.
1515
If you'd like to apply for one of these roles, please see the main [Community
1616
Team][communityteam] page.
1717

18+
1819
## Project Contributor
19-
### Who should apply:
20+
21+
**Who should apply:**
22+
2023
If you’ve contributed to a CC project, you should apply for this role.
2124

22-
### What does this role give you?
25+
**What does this role give you?**
26+
2327
- 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?**
2532

26-
### How can you engage with the community?
2733
You can use the following channels to engage with the community:
2834
- [Read access](/community/community-team/engagement-channels/#read-access) on
2935
the relevant repos on GitHub
3036
- Invitation to our Slack channels
31-
* [Newbie
37+
- [Newbie
3238
channels](/community/community-team/engagement-channels/#newbie-channels)
33-
* [UX design
39+
- [UX design
3440
channels](/community/community-team/engagement-channels/#ux-design-channel)
35-
* [Community Team
41+
- [Community Team
3642
channel](/community/community-team/engagement-channels/#community-team-channel)
3743
- Invitation to our
3844
[meetings](/community/community-team/engagement-channels/#meetings)
3945
- Membership in the [Community Team mailing
4046
list](/community/community-team/engagement-channels/#community-team-group)
4147

42-
### Guidelines for Project Contributors
48+
**Guidelines for Project Contributors**
49+
4350
If you’ve been accepted as a Project Contributor, you are encouraged to:
4451
- keep contributing to the project as and when you can!
4552
- 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+
4757

4858
## 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.
5159

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+
5368
- Everything a Project Contributor gets.
5469
- Creative Commons staff will write you a letter of recommendation on request.
5570

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:
5875
- [Triage access](/community/community-team/engagement-channels/#triage-access)
5976
on the relevant repos on GitHub
6077

61-
### Guidelines for Project Collaborators
78+
**Guidelines for Project Collaborators**
79+
6280
If you’ve been accepted as a Project Collaborator, you are encouraged to:
6381
- do everything a Project Contributor does.
6482
- review and triage new issues.
@@ -75,54 +93,65 @@ If you’ve been accepted as a Project Collaborator, you are encouraged to:
7593
**Note:** The role of Project Member was deprecated in July 2020 and all
7694
members were redesignated as collaborators.
7795

96+
7897
## Project Core Committer
7998

80-
### Who should apply:
99+
**Who should apply:**
100+
81101
If you’ve made many significant contributions to the project, know the codebase
82102
really well, and are interested in active maintenance of the project, you
83103
should apply.
84104

85-
### What does this role give you?
105+
**What does this role give you?**
86106

87107
- 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?**
90112

91-
### How can you engage with the community?
92113
In addition to the channels afforded to a Project Collaborator, you can use the
93114
following channels to engage with the community:
94115
- [Write access](/community/community-team/engagement-channels/#write-access)
95116
on the relevant repos on GitHub
96117

97-
### Guidelines for Project Core Committers
118+
**Guidelines for Project Core Committers**
119+
98120
If you’ve been accepted as a Project Core Committer, you are encouraged to:
99121
- do everything a Project Collaborator does.
100122
- merge PRs that you are confident work well and fit the project guidelines.
101123
- If you have any doubts, please check with project maintainers first!
102124
- proactively ask about mentorship opportunities if that interests you.
103125

126+
104127
## Project Maintainer
105128

106-
### Who should apply:
129+
**Who should apply:**
130+
107131
If you’re a Core Committer already and you’re interested in taking on
108132
maintainer responsibilities, you should apply. Please note that this role comes
109133
with a lot of responsibilities!
110134

111-
### What does this role give you?
135+
**What does this role give you?**
136+
112137
Everything a Project Core Committer gets.
113138

114-
### How can you engage with the community?
139+
**How can you engage with the community?**
140+
115141
In addition to the channels afforded to a Project Core Committer, you can use
116142
the following channels to engage with the community:
117143
- [Maintain
118144
access](/community/community-team/engagement-channels/#maintain-access) on
119145
the relevant repos on GitHub
120146

121-
### Guidelines for Project Maintainers
147+
**Guidelines for Project Maintainers**
148+
122149
Being a Project Maintainer comes with a larger set of responsibilities and
123150
guidelines, documented below:
124151

152+
125153
### Responsibilities
154+
126155
As a Project Maintainer, your responsibilities are as follows:
127156

128157
- **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.
148177
provide them with the link to the Community Team page on the CC Open Source
149178
site, and encourage them to apply.
150179

180+
151181
### Reviewing Community Team Applications
182+
152183
Applications for Community Team roles will be sent to you individually by the
153184
Open Source Community Coordinator (OSCC). The OSCC has ensured that the bare
154185
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:
176207
days or less from time of application to time of decision, but this is
177208
somewhat flexible.
178209

210+
179211
### Additional Notes
212+
180213
All Community Team work is done on a volunteer basis. Team members may pick up
181214
tasks and help out here and there if they would like, but they should not be
182215
expected to use all of their privileges all the time.

0 commit comments

Comments
 (0)