From 1aa70ee33dc1d2cc90c54d721b6b41bbb08161df Mon Sep 17 00:00:00 2001 From: Nikhita Raghunath Date: Thu, 11 Apr 2019 14:43:36 -0700 Subject: wg-governance: limit stakeholders to SIGs --- committee-steering/governance/wg-governance.md | 3 +-- 1 file changed, 1 insertion(+), 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? -- cgit v1.2.3