-
Criteria: At least a month of contributions.
-
Privileges:
-
Write access to upstream repo (push, edit label)
-
-
Activity level: Should contribute to most release cycles
-
Criteria: More than three months of active contributions.
-
Responsibilities:
-
Peer review other PRs
-
-
Activity level: Should contribute to almost all release cycles
-
Criteria: Has a deep knowledge of the respective feature/aspect/tech/tool.
-
Responsibilities:
-
Be main reviewer for PRs
-
Follow up on incoming issues related to the area
-
Fix critical/urgent issues in the area
-
-
Make releases as described in here
-
Activity level: Once per release cycle
-
Privileges: admin access to repo
-
Responsibilities:
-
Manage PRs through their life cycle
-
Assign reviewers
-
Deal with slow/inactive PRs
-
-
Can take part in issue triaging
-
-
Activity level: Daily
-
Criteria: Can advice devs based on,
-
extensive past experience with the project (e.g. someone who was an active developer for several years in the past)
-
deep expertise in some area relevant to the project (e.g. a domain expert)
-
-
Responsibilities:
-
Contributes to the project as a reviewer and an area expert
-
-
Active members
: Someone who contributes code/reviews to almost every release cycle, thereby helping to maintain the project velocity. -
Core members
: Those who are at level 2 (i.e.Committer
) or above and are 'active members'. -
Lead members
: Core members who are at level 4 or above. -
Past members
: Past core members who are no longer active.