Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: aburdenthehand <aburden@redhat.com>
Signed-off-by: Daniel Hiller <daniel.hiller.1972@googlemail.com>
  • Loading branch information
dhiller and aburdenthehand committed Jul 16, 2024
1 parent 497a25f commit 30ac69c
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 10 deletions.
16 changes: 8 additions & 8 deletions wg-TEMPLATE/README.md
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
# WG Responsibilities
# Working Group Responsibilities

All KubeVirt WGs must define a charter.
All KubeVirt Working Groups (WGs) must define a charter.

- The scope must define
- The scope must define:
- what problem the WG is solving
- what deliverable(s) will be produced to whom
- when the problem is solved
- The governance must outline
- the responsibilities within the WG as well as
- the roles owning those responsibilities.
- what deliverable(s) will be produced, and to whom
- when the problem is expected to be resolved
- The governance must outline:
- the responsibilities within the WG
- the roles owning those responsibilities
- which SIGs are stakeholders

## Steps to create a WG charter
Expand Down
4 changes: 2 additions & 2 deletions wg-TEMPLATE/wg-charter-template.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,8 @@ but not necessarily all of the internals.
### Stakeholder SIGs

A list of SIGs that are relevant to the WG.
The template may also mention
* which SIGs are more relevant than others,
The template may also mention:
* which SIGs are more relevant than others, and
* which subprojects are related to the WG

### Roles and responsibilities
Expand Down

0 comments on commit 30ac69c

Please sign in to comment.