From 594c06d3d22adce71d2b3c6d7e5f1864b67fdfc6 Mon Sep 17 00:00:00 2001 From: CyrusVorwald-ICON Date: Wed, 14 Sep 2022 15:35:50 -0400 Subject: [PATCH] docs: add sig and wg guidelines --- .../governance/sig-governance-guidelines.md | 5 ++- .../governance/wg-governance-guidelines.md | 44 +++++++++++++++++++ 2 files changed, 47 insertions(+), 2 deletions(-) create mode 100644 guidelines/governance/wg-governance-guidelines.md diff --git a/guidelines/governance/sig-governance-guidelines.md b/guidelines/governance/sig-governance-guidelines.md index 6ddacc3..098a4e3 100644 --- a/guidelines/governance/sig-governance-guidelines.md +++ b/guidelines/governance/sig-governance-guidelines.md @@ -1,4 +1,4 @@ -# SIG Governance Guidelines +# Special Interest Group Governance Guidelines The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and @@ -44,10 +44,11 @@ The technical lead MUST do the following: - Triage issues - Optimize software development lifecycle, process, and workflow +- Resolve cross-project technical issues ## Project management -Each SIG project MUST define the rationale, methodology, and public observability for +The SIG MUST define the rationale, methodology, and public observability for - how priorities are determined, staffed, managed, and accepted. - how target release dates are determined diff --git a/guidelines/governance/wg-governance-guidelines.md b/guidelines/governance/wg-governance-guidelines.md new file mode 100644 index 0000000..904bef0 --- /dev/null +++ b/guidelines/governance/wg-governance-guidelines.md @@ -0,0 +1,44 @@ +# Working Group Governance Guidelines + +The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL + NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and + "OPTIONAL" in this document are to be interpreted as described in + [RFC 2119](https://www.ietf.org/rfc/rfc2119.txt). + +## Introduction + +The purpose of this document is to describe working group (WG) practices and guidelines. WG members MUST adhere to these guidelines where applicable. + +### Relationship to SIGs + +All WGs MUST define their relationship to SIGs and follow the related SIGs guidelines. Deviation from related SIGs guidelines MUST be explicitly declared with stated rationale. + +## Leadership roles + +### Execution Lead + +The execution lead is responsible for the overall health and execution of the WG. The execution lead MUST: + +- Ensure that the WG goals and objectives are set +- Set WG priorities and roadmap +- Ensure that the WG adheres to the related SIGs guidelines +- Ensure that the WG has sufficient resources to succeed +- Ensure that WG progress reports are submitted on a monthly basis +- Facilitate communication and cross-SIG collaboration if the WG is related to multiple SIGs +- Take on technical lead role if the technical lead is not designated + +### Technical Lead + +The technical lead is responsible for the technical health and execution of the WG. The technical lead MUST: + +- Triage issues +- Ensure that the WG is adhering to the related SIGs technical guidelines + +## Disbanding + +WGs MUST disband if +- scope is completed +- there has been no communication activity for 1 month in the defined communications channels + +## Archiving +- WGs that disband MUST be archived in the [archives/working-groups](/archives/working-groups) folder.