docs: add charter templates #54
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -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). | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -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). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,40 @@ | ||
| # WG #WGNAME Charter | ||
|
Contributor
There was a problem hiding this comment. I'm not convinced that working groups should require a charter, especially one with a sponsor from the steering committee. I think as long as the special interest groups are approved, then they could be able to autonomously spawn working groups |
||
|
|
||
| | 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 | ||
|
Contributor
There was a problem hiding this comment. Disbanding is already mentioned in governance. Why not just link to that section? |
||
| 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 | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove "briefly"