Skip to content

Commit f8e693a

Browse files
kgodeykgodey
authored
Merge pull request creativecommons#541 from creativecommons/engagement_guide
Add engagement guide and update roles pages
2 parents 2f5991c + 949e090 commit f8e693a

File tree

6 files changed

+283
-84
lines changed

6 files changed

+283
-84
lines changed

‎.gitignore

+3
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,9 @@ venv
99
lektor/admin/static/gen
1010
assets/static/gen
1111

12+
.idea/
13+
.vscode/
14+
1215
node_modules
1316
gui/build
1417
gui/node_modules

‎content/community/community-team/community-building-roles/contents.lr

+33-30
Original file line numberDiff line numberDiff line change
@@ -12,55 +12,58 @@ Community building roles are for folks interested in helping grow CC's open sour
1212

1313
If you'd like to apply for one of these roles, please see the main [Community Team][communityteam] page.
1414

15-
## Community Contributor
16-
**Who should apply:** If you’ve helped anyone else in the CC open source community on GitHub, Slack, or email, you should apply for this role!
15+
## Community Collaborator
16+
**Who should apply:**
17+
If you’ve helped anyone else in the CC open source community on GitHub, Slack, or email and you’d like to do more to help grow the community, you should apply for this role!
1718

18-
**What does this role give you?**
19-
* You’ll receive invites to the private CC Community Team Slack channel and email list.
19+
**What does this role give you?**
2020
* You’ll receive previews of upcoming changes to the Community Team program.
2121
* You’ll be listed as [a member of the Community Team on CC Open Source](/community/community-team/members/).
2222

23+
**How can you engage with the community?**
24+
You can use the following channels to engage with the community:
25+
* [Edit access](/community/community-team/engagement-channels/#edit-access)
26+
on our upcoming tweets
27+
* Invitation to our Slack channels
28+
* [Newbie channels](/community/community-team/engagement-channels/#newbie-channels)
29+
* [UX design channels](/community/community-team/engagement-channels/#ux-design-channel)
30+
* [Community Team channel](/community/community-team/engagement-channels/#community-team-channel)
31+
* Invitation to our [meetings](/community/community-team/engagement-channels/#meetings)
32+
* Membership in the [Community Team mailing list](/community/community-team/engagement-channels/#community-team-group)
33+
2334
**Guidelines for Community Contributors**
2435
If you’ve been accepted as a Community Contributor, you are encouraged to:
2536
* keep helping people in the CC open source community!
26-
* respond to people on Slack
27-
* respond to questions or issues on GitHub
28-
* respond to people on the CC developer mailing list
37+
* Respond to people on Slack.
38+
* Respond to questions or issues on GitHub.
39+
* Respond to people on CC's mailing lists.
2940
* participate in discussions in Slack or via email.
30-
* contribute in other ways if you’d like, like writing code or reviewing pull requests.
31-
32-
## Community Collaborator
33-
**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!
34-
35-
**What does this role give you?**
36-
* Everything a Community Contributor gets.
37-
* Comment-only access to the Open Source Community project on Asana.
38-
* You’ll see our future plans for the open source community and have the opportunity to participate in them.
41+
* contribute in other ways if you’d like, like [writing code or reviewing pull requests](/community/community-team/project-roles/).
42+
* suggest improvements to, and new ideas for, the tweets from the [CC Open Source Twitter account](https://twitter.com/cc_opensource).
3943

40-
**Guidelines for Community Collaborators**
41-
If you’ve been accepted as a Community Collaborator, you are encouraged to:
42-
* do everything a Community Contributor does
43-
* participate in the Asana project and do some tasks on there
44-
* suggest Tweet ideas for the [CC Open Source Twitter account](https://twitter.com/cc_opensource)
44+
**Note:** The role of Community Contributor was deprecated in December 2020 and all members were redesignated as collaborators.
4545

4646
## Community Maintainer
47-
**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!
47+
**Who should apply:**
48+
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!
4849

49-
**What does this role give you?**
50+
**What does this role give you?**
5051
* Everything a Community Collaborator gets.
51-
* Full access to the Open Source Community project on Asana.
52-
* You’ll be able to add new tasks.
5352
* Manager permission on CC’s developer mailing list.
5453
* You’ll be able to approve new requests for people to join and moderate the list.
55-
* Access to tweet directly from CC Open Source account, if interested.
5654
* Creative Commons staff will write you a letter of recommendation on request.
57-
* CC swag sent to your house.
55+
* You'll receive CC swag.
56+
57+
**How can you engage with the community?**
58+
In addition to the channels afforded to a Community Collaborator, you can use the following channels to engage with the community:
59+
* [Publish access](/community/community-team/engagement-channels/#publish-access) on
60+
our upcoming tweets
5861

5962
**Guidelines for Community Maintainers**
6063
If you’ve been accepted as a Community Maintainer, you are encouraged to:
61-
* do everything a Community Collaborator does
62-
* respond to requests to join the CC developer mailing list
63-
* be available on Slack/email or GitHub regularly
64+
* do everything a Community Collaborator does.
65+
* respond to requests to join the CC developer mailing list.
66+
* be available on Slack/email or GitHub regularly.
6467
* ensure that people are getting the help they need on Slack and GitHub.
6568

6669
[communityteam]:/community/community-team/

‎content/community/community-team/engagement-channels/contents.lr

+191
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,191 @@
1+
_model: page
2+
---
3+
_template: page-with-toc.html
4+
---
5+
title: Community Team: Engagement Channels
6+
---
7+
description: This page serves as a guide for Community Team members on how to engage with CC Open Source across various channels.
8+
---
9+
is_long_page: true
10+
---
11+
body:
12+
13+
You've joined the CC Community Team. Congratulations! This is a very clear
14+
indication of your desire to engage more deeply with the Creative Commons
15+
community. As a fully remote organisation, CC uses a lot of tools to stay
16+
organised and collaborate. As you join the Community Team, depending on your
17+
role, you will be granted different levels of access to these tools and
18+
software.
19+
20+
Given the breadth and diversity of these tools coupled with varying levels of
21+
access, it can be easy to not know what is expected of you and how you can make
22+
the most of your involvement. This guide will condense this information down to
23+
help you identify the best ways to engage with the team. _Let's get started!_
24+
25+
## Meetings
26+
27+
We regularly hold meetings to discuss work and, occasionally, to play games.
28+
Based on your role and the project, you will be invited to some of these
29+
meetings. You can join the CC Engineering calendar to keep up with the schedule.
30+
31+
### Community meeting
32+
33+
In this meeting, all the staff and open-source community at CC meet to discuss
34+
work. Any major discussions and ideas that affect the projects or process take
35+
place in this meeting. It's also a channel to know what is happening in a
36+
parallel project that you don't get to interact with as much. We have a Show &
37+
Tell, so if you did or made something recently that you think is interesting,
38+
you can present that.
39+
40+
**Frequency:** monthly
41+
42+
### Vocabulary sprint planning
43+
44+
In this meeting, the Vocabulary sprint planning meeting is where all members
45+
involved in Vocabulary meet. This is mainly held to determine reasonable
46+
milestones on what can be accomplished in the next two weeks and assign
47+
different tasks and tickets to different people. If you'd like to get involved
48+
with Vocabulary code you can pick up some tasks here.
49+
50+
**Frequency:** fortnightly
51+
52+
## Slack
53+
54+
We communicate over text using Slack. Everyone from the community is on it,
55+
including CC employees. You can find fellow developers, technical writers and
56+
designers all in the same place. If you are, or want to be, a part of the
57+
community, [join us on Slack](/community/#slack). It is one of the best ways to
58+
connect with us.
59+
60+
Slack is organised by channels and, depending on your role, you will be invited
61+
to these channels to participate in discussions about certain topics.
62+
63+
### Newbie channels
64+
65+
There are a number of channels which budding open source developers join in
66+
hopes of finding like-minded developers. You should help them get started, clear
67+
simple doubts, introduce them to FOSS and make them feel welcome in our
68+
community. After all, the more the merrier!
69+
70+
**Channel:** `#general`, `#cc-dev-internships`, `#cc-developers`
71+
72+
### Community team channel
73+
74+
This is a channel where you can connect with other members of the Community
75+
Team. Announcements pertaining to the Community Team and planned changes to the
76+
community will be announced here first.
77+
78+
**Channel:** `#cc-dev-community-team`
79+
80+
### Engineering channel
81+
82+
This is a channel where the entire engineering team of CC can be reached.
83+
84+
**Channel:** `#engineering`
85+
86+
### UX design channels
87+
88+
This is the channel where we discuss design and UI/UX of various CC software and
89+
websites. This is particularly relevant to the Vocabulary project. The Figma
90+
specific channel mostly posts updates from the Figma documents of all the
91+
various projects.
92+
93+
**Channel:** `#ux-design`, `#ux-design-figma`
94+
95+
## Mailing lists
96+
97+
We also have a few mailing lists where we communicate announcements and the
98+
like. Join us on our [Google Group mailing lists](/community/#mailing-lists) if
99+
you are, or want to be, a part of the community.
100+
101+
### Developer group
102+
103+
This group is for all developers who are associated or related to the
104+
open-source community around our projects.
105+
106+
**Address:** cc-developers@creativecommons.org
107+
108+
### Usability Announcements group
109+
110+
This group is for all people participating in our Usability testing sessions.
111+
Announcements of upcoming tests are made in this group.
112+
113+
**Address:** usability-announce@creativecommons.org
114+
115+
### Community Team group
116+
117+
This group is for all CC tech staff and everyone on the Community Team.
118+
119+
**Address:** community-team@creativecommons.org
120+
121+
## GitHub
122+
123+
All our code is hosted on GitHub, we use issues to track bugs and identify
124+
features and pull requests to improve the software and drive it forward. All
125+
Community Team members with the role of
126+
[Project Collaborator](/community/community-team/project-roles/#project-collaborator)
127+
or higher are added to the
128+
[CC organisation](https://github.com/creativecommons/)
129+
on GitHub.
130+
131+
We use GitHub teams to manage access levels for all members of the organisation.
132+
Each role in a particular project corresponds to a certain access level over the
133+
repositories that are a part of that project. As you change your role, you will
134+
automatically be added to the appropriate team.
135+
136+
The [GitHub docs](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#repository-access-for-each-permission-level)
137+
are the best place to learn about these access levels.
138+
139+
### Read access
140+
141+
Read access offers no special privileges over issues or pull requests. You can
142+
nevertheless contribute to the repository by forking it to your account and
143+
making PRs as usual. You can also partake in discussions and help new
144+
contributors get started when fixing simpler issues.
145+
146+
### Triage access
147+
148+
Triage access grants you the privileges required to review incoming issues and
149+
classify them by priority, goal, value added to the project and so on and apply
150+
the appropriate labels to them. You will be added to a project's `CODEOWNERS`
151+
and will automatically be assigned PRs to review. You can approve them or
152+
request changes as necessary and can prevent a PR from being merged.
153+
154+
### Write access
155+
156+
Write access grants you the privileges required to create branches on the
157+
repository, push to the repository directly and merge pull requests that have
158+
been approved. You can even commit changes to open pull requests to make them
159+
ready for merge and can draft new releases for the project.
160+
161+
### Maintain access
162+
163+
Maintain access grants you the privileges to manage almost all aspects of the
164+
repository, except any destructive action or sensitive information. You can
165+
modify the repositories' topics, description and social cards among other
166+
settings.
167+
168+
## Twitter
169+
170+
Twitter is our preferred social media platform. We don't have a LinkedIn or
171+
Facebook presence. We generally post updates from our projects, introduce newly
172+
published blog posts, announce new releases of our software and any other
173+
interested information related to both FOSS and Creative Commons.
174+
175+
While [CC Open Source](https://twitter.com/cc_opensource) has a rather humble
176+
Twitter following, our tweets are often retweeted by
177+
[the parent Creative Commons handle](https://twitter.com/creativecommons).
178+
179+
### Edit access
180+
181+
You can see all the upcoming tweets from Creative Commons, suggest any
182+
improvements to the text or the material, suggest new topics for the tweets, and
183+
even write tweets that will be published, after review, from the official
184+
Twitter handle.
185+
186+
### Publish access
187+
188+
You can post or schedule the tweets to be published from the official Twitter
189+
handle. You can also interact with the open source community on Twitter and
190+
access the official Twitter stats to further improve our outreach and engagement
191+
metrics.

0 commit comments

Comments
 (0)