diff options
| author | Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> | 2019-04-12 14:31:52 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-04-12 14:31:52 -0700 |
| commit | 46f90e97228fd60b4ecb951f1f9f7e67be31f439 (patch) | |
| tree | 0c9872b29fc4ee09cc829ebc2e95b143c2791049 | |
| parent | 968cefa1dab96dbcaaee865737ef6b8736758ef1 (diff) | |
| parent | 1aa70ee33dc1d2cc90c54d721b6b41bbb08161df (diff) | |
Merge pull request #3576 from nikhita/fix-stakeholders
wg-governance: limit stakeholders to SIGs
| -rw-r--r-- | committee-steering/governance/wg-governance.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/committee-steering/governance/wg-governance.md b/committee-steering/governance/wg-governance.md index 16f9a88f..9f729a0e 100644 --- a/committee-steering/governance/wg-governance.md +++ b/committee-steering/governance/wg-governance.md @@ -65,8 +65,7 @@ should eventually be reflected in a pull request on sigs.yaml: 1. What is the artifact that this group will deliver, and to whom? 1. How does the group know when the problem solving process is completed, and it is time for the Working Group to dissolve? -1. Who are all of the stakeholders involved in this problem this group is trying to solve (SIGs, steering committee, - other Working Groups)? +1. Who are all of the stakeholder SIGs involved in this problem this group is trying to solve? 1. What are the meeting mechanics (frequency, duration, roles)? 1. Does the goal of the Working Group represent the needs of the project as a whole, or is it focused on the interests of a narrow set of contributors or companies? |