kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #319 from kubernetes/mml-patch-1 

Update on-call-build-cop.md
This commit is contained in:
Matt Liggett 2017-02-01 13:17:29 -08:00 committed by GitHub
parent 3c460f81e8 3c12ad1f83
commit f6f621aea5
1 changed files with 6 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
contributors/devel/on-call-build-cop.md
View File

@ -7,9 +7,9 @@
### Traffic sources and responsibilities ### Traffic sources and responsibilities
* GitHub Kubernetes [issues](https://github.com/kubernetes/kubernetes/issues) * GitHub Kubernetes [issues](https://github.com/kubernetes/kubernetes/issues):
and [pulls](https://github.com/kubernetes/kubernetes/pulls): Your job is to be Your job is to be
the first responder to all new issues and PRs. If you are not equipped to do the first responder to all new issues. If you are not equipped to do
this (which is fine!), it is your job to seek guidance! this (which is fine!), it is your job to seek guidance!
* Support issues should be closed and redirected to Stackoverflow (see example * Support issues should be closed and redirected to Stackoverflow (see example
@ -35,18 +35,12 @@ This is the only situation in which you should add a priority/* label
* Assign any issues related to Vagrant to @derekwaynecarr (and @mention him * Assign any issues related to Vagrant to @derekwaynecarr (and @mention him
in the issue) in the issue)
* All incoming PRs should be assigned a reviewer. * Keep in mind that you can @ mention people in an issue to bring it to
* unless it is a WIP (Work in Progress), RFC (Request for Comments), or design proposal.
* An auto-assigner [should do this for you] (https://github.com/kubernetes/kubernetes/pull/12365/files)
* When in doubt, choose a TL or team maintainer of the most relevant team; they can delegate
* Keep in mind that you can @ mention people in an issue/PR to bring it to
their attention without assigning it to them. You can also @ mention github their attention without assigning it to them. You can also @ mention github
teams, such as @kubernetes/goog-ux or @kubernetes/kubectl teams, such as @kubernetes/goog-ux or @kubernetes/kubectl
* If you need help triaging an issue or PR, consult with (or assign it to) * If you need help triaging an issue, consult with (or assign it to)
@brendandburns, @thockin, @bgrant0607, @quinton-hoole, @davidopp, @dchen1107, @brendandburns, @thockin, @bgrant0607, @davidopp, @dchen1107,
@lavalamp (all U.S. Pacific Time) or @fgrzadkowski (Central European Time). @lavalamp (all U.S. Pacific Time) or @fgrzadkowski (Central European Time).
* At the beginning of your shift, please add team/* labels to any issues that * At the beginning of your shift, please add team/* labels to any issues that