diff options
| author | Ihor Dvoretskyi <ihor@dvoretskyi.com> | 2017-04-13 21:16:44 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-04-13 21:16:44 +0300 |
| commit | de77de5396a310214eecd21342093f834fff62c3 (patch) | |
| tree | f75947147355e592ce51db5418bbbfd95508e200 /governance.md | |
| parent | e73af0d00f747f39b52e72615d5a003bb09aaa2e (diff) | |
PM SIG representatives linked
Diffstat (limited to 'governance.md')
| -rw-r--r-- | governance.md | 8 |
1 files changed, 1 insertions, 7 deletions
diff --git a/governance.md b/governance.md index 29a7e221..bc38405f 100644 --- a/governance.md +++ b/governance.md @@ -186,13 +186,7 @@ In order to standardize Special Interest Group efforts, create maximum transpare * Participate in release planning meetings and retrospectives, and burndown meetings, as needed * Ensure related work happens in a project-owned github org and repository, with code and tests explicitly owned and supported by the SIG, including issue triage, PR reviews, test-failure response, bug fixes, etc. * Use the above forums as the primary means of working, communicating, and collaborating, as opposed to private emails and meetings -* Represent the SIG for the PM group: - * identify all features in the current release from the SIG - * track all features (in the repo with all the fields complete) - * attend your SIG meetings - * attend the PM group meetings which occur 3-5 times per release - * identify the annual roadmap - * advise their SIG as needed +* Represent the SIG for the PM group - see [PM SIG representatives](https://github.com/kubernetes/community/blob/master/sig-pm/SIG%20PM%20representatives.md). # CLA |