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
+
23
31
**Guidelines for Community Contributors**
24
32
If you’ve been accepted as a Community Contributor, you are encouraged to:
25
33
* 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
34
+
* respond to people on Slack.
35
+
* respond to questions or issues on GitHub.
36
+
* respond to people on CC's mailing lists.
29
37
* participate in discussions in Slack or via email.
30
-
* contribute in other ways if you’d like, like writing code or reviewing pull requests.
38
+
* contribute in other ways if you’d like, like [writing code or reviewing pull requests](/community/community-team/project-roles/).
31
39
32
40
## Community Collaborator
33
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!
@@ -37,11 +45,20 @@ If you’ve been accepted as a Community Contributor, you are encouraged to:
37
45
* Comment-only access to the Open Source Community project on Asana.
38
46
* You’ll see our future plans for the open source community and have the opportunity to participate in them.
39
47
48
+
**How can you engage with the community?**
49
+
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:
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)
59
+
* do everything a Community Contributor does.
60
+
* participate in the Asana project and do some tasks on there.
61
+
* suggest Tweet ideas for the [CC Open Source Twitter account](https://twitter.com/cc_opensource).
45
62
46
63
## Community Maintainer
47
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!
@@ -52,15 +69,19 @@ If you’ve been accepted as a Community Collaborator, you are encouraged to:
52
69
* You’ll be able to add new tasks.
53
70
* Manager permission on CC’s developer mailing list.
54
71
* 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.
56
72
* Creative Commons staff will write you a letter of recommendation on request.
57
-
* CC swag sent to your house.
73
+
* You'll receive CC swag.
74
+
75
+
**How can you engage with the community?**
76
+
In addition to the channels afforded to a Community Collaborator, you can use the following channels to engage with the community:
77
+
*[Compose access](/community/community-team/engagement-channels/#compose-access) on
78
+
our upcoming tweets
58
79
59
80
**Guidelines for Community Maintainers**
60
81
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
82
+
* do everything a Community Collaborator does.
83
+
* respond to requests to join the CC developer mailing list.
84
+
* be available on Slack/email or GitHub regularly.
64
85
* ensure that people are getting the help they need on Slack and GitHub.
Copy file name to clipboardExpand all lines: content/community/community-team/project-roles/contents.lr
+43-23
Original file line number
Diff line number
Diff line change
@@ -16,71 +16,91 @@ If you'd like to apply for one of these roles, please see the main [Community Te
16
16
**Who should apply:** If you’ve contributed to a CC project, you should apply for this role.
17
17
18
18
**What does this role give you?**
19
-
* You’ll receive invites to the private CC Community Team Slack channel and email list.
20
19
* You’ll receive previews of upcoming changes to the Community Team program.
21
20
* You’ll be listed as [a member of the Community Team on CC Open Source](/community/community-team/members/).
22
21
22
+
**How can you engage with the community?**
23
+
You can use the following channels to engage with the community:
24
+
*[Read access](/community/community-team/engagement-channels/#read-access) on
25
+
the relevant repos on GitHub
26
+
*[Community Team Slack channel](/community/community-team/engagement-channels/#community-team-channel)
27
+
*[Community Team mailing list](/community/community-team/engagement-channels/#community-team-group)
28
+
23
29
**Guidelines for Project Contributors**
24
30
If you’ve been accepted as a Project Contributor, you are encouraged to:
25
-
* keep contributing to the project as and when you can.
31
+
* keep contributing to the project as and when you can!
26
32
* participate in discussions in Slack or via email.
27
-
*review pull requests opened by other contributors.
33
+
*contribute in other ways if you'd like, like [helping out newbie developers or voting on our tweets](/community/community-team/community-building-roles/).
28
34
29
35
## Project Collaborator
30
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.
31
37
32
38
**What does this role give you?**
33
39
* Everything a Project Contributor gets.
34
-
* You’ll be added to the `creativecommons` GitHub organization and given [Triage](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) permissions to the project repository.
35
-
* You’ll be able to assign people and change labels on GitHub issues associated with the project.
36
-
* You’ll be added to the `CODEOWNERS` file for the project.
37
-
* This will allow your PR reviews to block merge.
38
-
* This will auto assign you PRs to review.
39
-
* You’ll receive invites to some of CC’s internal meetings, Asana projects, and/or Slack channels.
40
-
* The specifics depend on the project.
41
40
* Creative Commons staff will write you a letter of recommendation on request.
42
41
42
+
**How can you engage with the community?**
43
+
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:
45
-
* do everything a Project Contributor does
46
-
* review and triage new issues
47
-
* ask the issue author for more details if appropriate
48
-
* check with the project maintainers if the issue makes sense
49
-
* update the labels on the issue appropriately once you have all the information you need (e.g. remove “awaiting triage” label)
59
+
* do everything a Project Contributor does.
60
+
* 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).
50
64
* review assigned pull requests to unblock merges.
51
65
* participate in discussions in the new meetings and channels you’ve been added to.
52
66
* identify promising contributors to the project and invite them to join the Community Team.
53
67
54
-
**Note**
55
-
The role of Project Member was deprecated in July 2020 and all members were redesignated as collaborators.
68
+
**Note:** The role of Project Member was deprecated in July 2020 and all members were redesignated as collaborators.
56
69
57
70
## Project Core Committer
58
-
**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.
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.
59
72
60
73
**What does this role give you?**
61
74
* Everything a Project Collaborator gets.
62
-
* You’ll be given [Write]((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) permissions to the project repository.
63
-
* This will allow you to merge PRs.
64
75
* You’ll be eligible to mentor GSoC and Outreachy interns (and similar) for Creative Commons.
65
76
* You'll receive CC swag.
66
77
78
+
**How can you engage with the community?**
79
+
In addition to the channels afforded to a Project Collaborator, you can use the following channels to engage with the community:
If you’ve been accepted as a Project Core Committer, you are encouraged to:
69
-
* do everything a Project Collaborator does
85
+
* do everything a Project Collaborator does.
70
86
* merge PRs that you are confident work well and fit the project guidelines.
71
87
* if you have any doubts, please check with project maintainers first!
72
88
* proactively ask about mentorship opportunities if that interests you.
73
-
* recognize other contributions with “Great Contribution” labels
89
+
* recognize other contributions with “Great Contribution” labels
74
90
* more details are available in the "Great Contribution" section in the Project Maintainer guidelines below.
75
91
76
92
## Project Maintainer
77
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!
78
94
79
95
**What does this role give you?**
80
96
* Everything a Project Core Committer gets.
81
-
* You’ll be given [Maintain]((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) permissions to the project repository.
82
97
* This will allow you to manage some repository settings.
83
98
99
+
**How can you engage with the community?**
100
+
In addition to the channels afforded to a Project Core Committer, you can use the following channels to engage with the community:
0 commit comments