Skip to content

Commit 2c2f550

Browse files
authored
Merge pull request #1608 from riaankleinhans/add-governance-review-request-issue-temple
Add governance review request issue temple
2 parents 983d915 + 0322aa0 commit 2c2f550

File tree

1 file changed

+158
-0
lines changed

1 file changed

+158
-0
lines changed
Lines changed: 158 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,158 @@
1+
name: Governance review request
2+
description: Ask for a governance review for your project from TAG Contributor Strategy
3+
title: "[Governance Review]: PROJECT NAME"
4+
labels: ["wg/governance", "project-governance-review"]
5+
assignees:
6+
- jberkus
7+
- geekygirldawn
8+
body:
9+
- type: markdown
10+
attributes:
11+
value: |
12+
Thank you for your interest in having a governance review request from TAG Contributor Strategy.
13+
For more information on what a governance is, please visit our [governance documentation](https://contribute.cncf.io/maintainers/governance/overview/).
14+
---
15+
This form helps CNCF TAG Contributor Strategy understand your project's governance structure and assess its readiness for a review.
16+
For assistance, please contact us at [#tag-contributor-strategy](https://cloud-native.slack.com/archives/CT6CWS1JN) channel on CNCF Slack.
17+
18+
- type: markdown
19+
attributes:
20+
value: |
21+
## Project information
22+
23+
- type: input
24+
attributes:
25+
label: Project Name
26+
validations:
27+
required: true
28+
29+
- type: input
30+
attributes:
31+
label: Project Website
32+
validations:
33+
required: true
34+
35+
- type: markdown
36+
attributes:
37+
value: |
38+
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.
39+
40+
- type: input
41+
attributes:
42+
label: Contact Details 1
43+
placeholder: ex. @githubHandle
44+
validations:
45+
required: true
46+
- type: input
47+
attributes:
48+
label: Contact Details 2
49+
placeholder: ex. @githubHandle
50+
validations:
51+
required: true
52+
53+
- type: input
54+
attributes:
55+
label: Links to communication channels
56+
placeholder: ex. Slack, WhatsApp, etc.
57+
description: |
58+
Please provide us with the communication channel link to reach out to you if needed.
59+
validations:
60+
required: true
61+
62+
- type: dropdown
63+
attributes:
64+
label: Reason for governance review request
65+
description: |
66+
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.
67+
options:
68+
- CNCF Sandbox acceptance application
69+
- Application for moving levels from Sandbox to Incubation
70+
- Application for moving levels from Incubation to Graduation
71+
- Other (please specify in the “Additional Notes” input at the end of this form)
72+
validations:
73+
required: true
74+
75+
- type: markdown
76+
attributes:
77+
value: |
78+
## Governance Information
79+
80+
- type: textarea
81+
attributes:
82+
label: Governance model
83+
description: |
84+
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.
85+
If not, please write a short description of your governance model.
86+
validations:
87+
required: true
88+
89+
- type: textarea
90+
attributes:
91+
label: Link to Incubating/Graduation/Sandbox Application
92+
description: |
93+
If your project is in the process of moving levels or being accepted into the CNCF please link to the Issue or PR for that event. If for Incubation or Graduation, please fill out all items in the appropriate sections of that application (Governance and Contributing) before applying for a governance review.
94+
validations:
95+
required: true
96+
97+
- type: textarea
98+
attributes:
99+
label: Governance documents
100+
description: |
101+
Please provide the governance documentation of your project in separate lines. This would include links to documents that explain:
102+
- Project purpose
103+
- Maintainer List (with employer information)
104+
- How your project is making decisions
105+
- How and when contributors are moving through the contributor ladder (e.g. becoming a maintainer)
106+
- Maintainer life cycle with information about how and when maintainers are demoted
107+
- Code of Conduct
108+
- Contributor Guide
109+
- How your community conduct communication and meetings
110+
- How your community handles security reporting and response
111+
- Who owns what code and docs
112+
113+
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.
114+
115+
If these documents are already linked from an Incubation or Graduation application, you may simply
116+
refer to that document by linking it here, and fill in only the documents not listed there.
117+
validations:
118+
required: true
119+
120+
- type: textarea
121+
attributes:
122+
label: Governance Execution Examples
123+
description: |
124+
Do you have any examples of execution of the governance? Examples could be:
125+
- Voting
126+
- Promoting a contributor / demoting a maintainer
127+
- Security response
128+
- Meeting recordings
129+
validations:
130+
required: true
131+
132+
- type: textarea
133+
attributes:
134+
label: Governance Evolution
135+
description: |
136+
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.
137+
138+
If there are any major milestones in the project's governance over time, please describe them here with supporting URL links.
139+
validations:
140+
required: true
141+
142+
- type: markdown
143+
attributes:
144+
value: |
145+
## Additional information
146+
147+
- type: textarea
148+
attributes:
149+
label: Any specific aspects of your governance structure are you seeking feedback on?
150+
151+
- type: textarea
152+
attributes:
153+
label: Do you have any concerns or specific areas where you feel your governance could be improved?
154+
155+
- type: textarea
156+
attributes:
157+
label: Additional notes and resources
158+
description: Please add any additional notes and resources here.

0 commit comments

Comments
 (0)