From 4611e66df81288a44c61be25e180fa8174c43a78 Mon Sep 17 00:00:00 2001 From: CyrusVorwald-ICON Date: Wed, 14 Sep 2022 15:45:53 -0400 Subject: [PATCH] docs(sig, wg, committee): add charter templates --- .../charter/committee-charter-template.md | 28 +++++++++++++ templates/charter/sig-charter-template.md | 28 +++++++++++++ templates/charter/wg-charter-template.md | 40 +++++++++++++++++++ 3 files changed, 96 insertions(+) create mode 100644 templates/charter/committee-charter-template.md create mode 100644 templates/charter/sig-charter-template.md create mode 100644 templates/charter/wg-charter-template.md diff --git a/templates/charter/committee-charter-template.md b/templates/charter/committee-charter-template.md new file mode 100644 index 0000000..cd29302 --- /dev/null +++ b/templates/charter/committee-charter-template.md @@ -0,0 +1,28 @@ +# Committee #COMMITTEENAME Charter + +| Status | (Proposed / Accepted / Rejected / Archived) | +:-------------- |:---------------------------------------------------- | +| **PR Link** | [PR #](https://github.com/icon-project/community/pulls/#) (update when you have PR link)| +| **Author(s)** | My Name (me@example.org), AN Other (you@example.org) | +| **Sponsor** | Steering committee member name (example@icon.foundation) | +| **Updated** | DD MONTH YYYY | + +## Overview + +Briefly explain to the community why your committee could matter to them. + +## Scope + +Briefly describe all technical and non-technical components within the scope of the committee. + +### Out of scope + +Briefly clarify anything that could be considered to be in scope but are not. + +## Governance + +This committee adheres to the [committee governance guidelines](/guidelines/governance/committee-governance-guidelines.md). Any changes from the guidelines should be noted here. + +### Roles and Responsibilities + +Briefly describe the roles and responsibilities of various members of the committee that are not defined in the [committee governance guidelines](/guidelines/governance/committee-governance-guidelines.md). diff --git a/templates/charter/sig-charter-template.md b/templates/charter/sig-charter-template.md new file mode 100644 index 0000000..36f7a1a --- /dev/null +++ b/templates/charter/sig-charter-template.md @@ -0,0 +1,28 @@ +# SIG #SIGNAME Charter + +| Status | (Proposed / Accepted / Rejected / Archived) | +:-------------- |:---------------------------------------------------- | +| **PR Link** | [PR #](https://github.com/icon-project/community/pulls/#) (update when you have PR link)| +| **Author(s)** | My Name (me@example.org), AN Other (you@example.org) | +| **Sponsor** | Steering committee member name (example@icon.foundation) | +| **Updated** | DD MONTH YYYY | + +## Overview + +Briefly explain to the community why your SIG could matter to them. + +## Scope + +Briefly describe all technical and non-technical components within the scope of the SIG. + +### Out of scope + +Briefly clarify anything that could be considered to be in scope but are not. + +## Governance + +This SIG adheres to the [SIG governance guidelines](/guidelines/governance/sig-governance-guidelines.md). Any changes from the guidelines should be noted here. + +### Roles and Responsibilities + +Briefly describe the roles and responsibilities of various members of the SIG that are not defined in the [SIG governance guidelines](/guidelines/governance/sig-governance-guidelines.md). diff --git a/templates/charter/wg-charter-template.md b/templates/charter/wg-charter-template.md new file mode 100644 index 0000000..8a48f69 --- /dev/null +++ b/templates/charter/wg-charter-template.md @@ -0,0 +1,40 @@ +# WG #WGNAME Charter + +| Status | (Proposed / Accepted / Rejected / Archived) | +:-------------- |:---------------------------------------------------- | +| **PR Link** | [PR #](https://github.com/icon-project/community/pulls/#) (update when you have PR link)| +| **Author(s)** | My Name (me@example.org), AN Other (you@example.org) | +| **Sponsor** | Steering committee member name (example@icon.foundation) | +| **Updated** | DD MONTH YYYY | + +This charter adheres to the [WG governance guidelines](/guidelines/governance/wg-governance-guidelines.md). + +## Overview + +Briefly explain to the community why your WG could matter to them. + +## Relationship to SIGs + +Describe + +## Scope + +Describe all technical and non-technical components within the scope of the WG. + +### Out of scope + +Clarify anything that could be considered to be in scope but are not. + +## Governance + +This WG adheres to the [WG governance guidelines](/guidelines/governance/wg-governance-guidelines.md). Any changes from the guidelines should be noted here. + +### Roles and Responsibilities + +Briefly describe the roles and responsibilities of various members of the WG that are not defined in the [WG governance guidelines](/guidelines/governance/wg-governance-guidelines.md). + +## Disbanding +The WG must disband if +- Scope of the WG is completed +- The WG is inactive for 1 month +- The technical steering committee determines that the WG should disband for some specified reason