forked from kubernetes/community
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
ae25a65
commit 859d2dd
Showing
2 changed files
with
47 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
## Kubernetes Project Managers | ||
|
||
kubernetes-project-managers is a github team that will help to manage and maintain the project in ways other than just writing code. Specifically, members of the kubernetes-project-managers team are | ||
expected to: | ||
|
||
* Add/change routing labels to issues (team/, area/, component/) | ||
* Apply release-note labels to PRs (until that is automated or eliminated) | ||
* Set the milestone on a PR or issue | ||
* Assign issues to the correct people for immediate triage/work | ||
* Assign PRs to be reviewed by the correct people | ||
* Close duplicate, stale, misplaced issues | ||
* Close support issues, with a redirect to stackoverflow | ||
|
||
They should **NOT**: | ||
|
||
* Manually apply merge labels to PRs (lgtm, approved) or press merge button | ||
* Apply priority labels to PRs | ||
* Apply cherrypick labels to PRs | ||
* Edit text of other people's PRs and issues, including deleting comments | ||
* Modify anyone else’s release note | ||
* Create, edit, delete labels | ||
* Create, edit, close, delete milestones | ||
* Create, edit, delete releases | ||
* Create, edit, delete PR statuses | ||
* Edit wiki | ||
|
||
Abuse and misuse will result in prompt removal from the Project Managers group and loss of privileges. | ||
|
||
## Joining the group | ||
|
||
The following is the provisional process for adding people to the group: | ||
|
||
1. Join kubernetes-wg-contribex at googlegroups.com. Send a message to that group that states: | ||
1. Your github id. | ||
1. What you are working on with respect to the project. | ||
1. Any official management or leadership responsibilities you may have (e.g., manager of a team that includes the following contributors: ….). | ||
1. What you plan to do with the powers, including specific labels, SIGs, system components, github teams, etc. | ||
1. How long you think you need the powers. | ||
1. Any questions you have about appropriate application of the powers (e.g., policy for assigning priorities to issues, policy for assigning and unassigning issues, which parts of the system are covered by which teams). | ||
|
||
|
||
The Contributor Experience working-group leads or Brian Grant (@bgrant0607) will approve or deny your request. | ||
|
||
Some prerequisites may need to be completed prior to being added to the github team, such as clarifying relevant policies in our contributor documentation. | ||
|
||
Thanks for helping to manage the project! |