Skip to content

Commit

Permalink
Governance review request issue template (#572)
Browse files Browse the repository at this point in the history
Signed-off-by: Ali Ok <[email protected]>
  • Loading branch information
aliok authored Jan 14, 2024
1 parent d43866c commit a249311
Showing 1 changed file with 158 additions and 0 deletions.
158 changes: 158 additions & 0 deletions .github/ISSUE_TEMPLATE/governance-review-request.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,158 @@
name: Governance review request
description: Ask for a governance review for your project from TAG Contributor Strategy
title: "[Governance Review]: PROJECT NAME"
labels: ["wg/governance"]
assignees:
- jberkus
- aliok
- geekygirldawn
body:
- type: markdown
attributes:
value: |
Thank you for your interest in having a governance review request from TAG Contributor Strategy.
For more information on what a governance is, please visit our [governance documentation](https://contribute.cncf.io/maintainers/governance/overview/).
---
This form helps CNCF TAG Contributor Strategy understand your project's governance structure and assess its readiness for a review.
For assistance, please contact us at [#tag-contributor-strategy](https://cloud-native.slack.com/archives/CT6CWS1JN) channel on CNCF Slack.
- type: markdown
attributes:
value: |
## Project information
- type: input
attributes:
label: Project Name
validations:
required: true

- type: input
attributes:
label: Project Website
validations:
required: true

- type: markdown
attributes:
value: |
Please provide at least 2 people who are able to help us understand the governance of your project, in case there is material that is not clear.
- type: input
attributes:
label: Contact Details 1
placeholder: ex. @githubHandle
validations:
required: true
- type: input
attributes:
label: Contact Details 2
placeholder: ex. @githubHandle
validations:
required: true

- type: input
attributes:
label: Links to communication channels
placeholder: ex. Slack, WhatsApp, etc.
description: |
Please provide us with the communication channel link to reach out to you if needed.
validations:
required: true

- type: dropdown
attributes:
label: Reason for governance review request
description: |
What is the reason for your governance review request? This will help us understand the context of your request, help us prioritize it and also help us understand what you are looking for from the review.
options:
- CNCF Sandbox acceptance application
- Application for moving levels from Sandbox to Incubation
- Application for moving levels from Incubation to Graduation
- Other (please specify in the “Additional Notes” input at the end of this form)
validations:
required: true

- type: textarea
attributes:
label: Are there any sub-projects, plugins, and related?
description: |
If your project includes the sub-projects, plugins, and other notable divisions, please write them here.
validations:
required: true

- type: markdown
attributes:
value: |
## Governance information
- type: textarea
attributes:
label: Governance model
description: |
If your project governance is based on one of the [CNCF governance templates](https://contribute.cncf.io/maintainers/templates/governance-intro/), please indicate which one it is here, with any differences for your project.
If not, please write a short description of your governance model.
validations:
required: true

- type: textarea
attributes:
label: Governance documents
description: |
Please provide the governance documentation of your project in separate lines. This would include links to documents that explain:
- Project purpose
- Maintainer List (with employer information)
- How your project is making decisions
- How and when contributors are moving through the contributor ladder (e.g. becoming a maintainer)
- Maintainer life cycle with information about how and when maintainers are demoted
- Code of Conduct
- Contributor Guide
- How your community conduct communication and meetings
- How your community handles security reporting and response
- Who owns what code and docs
These documents do NOT need to be separate documents. Single document or a few documents that explain everything above is good for us to read, understand and evaluate your project governance.
**NOTE**: Make sure you provide links to these documents as snapshots with commit hashes and use the same commit for all links from the same repository. Example: `https://github.com/FOO/BAR/blob/<commitHash>/path/to/doc.md`
validations:
required: true

- type: textarea
attributes:
label: Governance Execution Examples
description: |
Do you have any examples of execution of the governance? Examples could be:
- Voting
- Promoting a contributor / demoting a maintainer
- Security response
- Meeting recordings
validations:
required: true

- type: textarea
attributes:
label: Governance Evolution
description: |
Governance evolution is the observable changes and improvements the project makes to its governance over the project's lifespan. It is expected that changes will occur over the project's life and that such changes are iterative, tested, and adjusted.
If there are any major milestones in the project's governance over time, please describe them here with supporting URL links.
validations:
required: true

- type: markdown
attributes:
value: |
## Additional information
- type: textarea
attributes:
label: Any specific aspects of your governance structure are you seeking feedback on?

- type: textarea
attributes:
label: Do you have any concerns or specific areas where you feel your governance could be improved?

- type: textarea
attributes:
label: Additional notes and resources
description: Please add any additional notes and resources here.

0 comments on commit a249311

Please sign in to comment.