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
Copy file name to clipboardExpand all lines: content/community/community-team/project-roles/contents.lr
+10-17
Original file line number
Diff line number
Diff line change
@@ -25,28 +25,14 @@ If you’ve been accepted as a Project Contributor, you are encouraged to:
25
25
* participate in discussions in Slack or via email.
26
26
* review pull requests opened by other contributors.
27
27
28
-
## Project Member
29
-
**Who should apply:** If you’ve made multiple contributions that took you a couple of hours each to complete, you should apply for this role.
28
+
## Project Collaborator
29
+
**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.
30
30
31
31
**What does this role give you?**
32
32
* Everything a Project Contributor gets.
33
33
* 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.
34
34
* You’ll receive previews of upcoming changes to the Community Team program.
35
35
* You’ll be able to assign people and change labels on GitHub issues associated with the project.
36
-
37
-
**Guidelines for Project Members**
38
-
If you’ve been accepted as a Project Member, you are encouraged to:
39
-
* do everything a Project Contributor does
40
-
* review and triage new issues
41
-
* ask the issue author for more details if appropriate
42
-
* check with the project maintainers if the issue makes sense
43
-
* update the labels on the issue appropriately once you have all the information you need (e.g. remove “awaiting triage” label)
44
-
45
-
## Project Collaborator
46
-
**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.
47
-
48
-
**What does this role give you?**
49
-
* Everything a Project Member gets.
50
36
* You’ll be added to the `CODEOWNERS` file for the project.
51
37
* This will allow your PR reviews to block merge.
52
38
* This will auto assign you PRs to review.
@@ -56,11 +42,18 @@ If you’ve been accepted as a Project Member, you are encouraged to:
56
42
57
43
**Guidelines for Project Collaborators**
58
44
If you’ve been accepted as a Project Collaborator, you are encouraged to:
59
-
* do everything a Project Member does
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)
60
50
* review assigned pull requests to unblock merges.
61
51
* participate in discussions in the new meetings and channels you’ve been added to.
62
52
* identify promising contributors to the project and invite them to join the Community Team.
63
53
54
+
**Note**
55
+
The role of Project Member was deprecated in July 2020 and all members were redesignated as collaborators.
56
+
64
57
## Project Core Committer
65
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.
0 commit comments