Skip to content

Commit f13dff3

Browse files
committed
Merge Project Member into Project Collaborator
1 parent 26890d3 commit f13dff3

File tree

1 file changed

+10
-17
lines changed
  • content/community/community-team/project-roles

1 file changed

+10
-17
lines changed

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

+10-17
Original file line numberDiff line numberDiff line change
@@ -25,28 +25,14 @@ If you’ve been accepted as a Project Contributor, you are encouraged to:
2525
* participate in discussions in Slack or via email.
2626
* review pull requests opened by other contributors.
2727

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.
3030

3131
**What does this role give you?**
3232
* Everything a Project Contributor gets.
3333
* 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.
3434
* You’ll receive previews of upcoming changes to the Community Team program.
3535
* 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.
5036
* You’ll be added to the `CODEOWNERS` file for the project.
5137
* This will allow your PR reviews to block merge.
5238
* 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:
5642

5743
**Guidelines for Project Collaborators**
5844
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)
6050
* review assigned pull requests to unblock merges.
6151
* participate in discussions in the new meetings and channels you’ve been added to.
6252
* identify promising contributors to the project and invite them to join the Community Team.
6353

54+
**Note**
55+
The role of Project Member was deprecated in July 2020 and all members were redesignated as collaborators.
56+
6457
## Project Core Committer
6558
**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.
6659

0 commit comments

Comments
 (0)