Skip to content

Commit 3a985ca

Browse files
committed
add k8gb governance review
Signed-off-by: Josh Gavant <joshgavant@gmail.com>
1 parent 31921b2 commit 3a985ca

File tree

1 file changed

+255
-0
lines changed

1 file changed

+255
-0
lines changed
Lines changed: 255 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,255 @@
1+
# k8gb - Governance Review - 2026-01-21
2+
3+
What follows is a governance review and assessment for the k8gb project. The
4+
review was executed as part of due diligence when k8gb submitted to move to
5+
Incubation level at CNCF in <https://github.com/cncf/toc/issues/1472>.
6+
7+
- Project: <https://github.com/k8gb-io/k8gb>
8+
- Site: <https://www.k8gb.io/>
9+
- Matriculation issue: <https://github.com/cncf/toc/issues/1472>
10+
- Governance review issue: <https://github.com/cncf/toc/issues/1963>
11+
12+
This review is based on the template at
13+
<https://github.com/cncf/toc/blob/main/toc_subprojects/project-reviews-subproject/governance-review-template.md>
14+
15+
## Summary and Assessment
16+
17+
**Status:** Satisfactory
18+
19+
### Must-Fix Items
20+
21+
**The following issues have been identified that need to be resolved before
22+
[project milestone or other requirement]:**
23+
24+
- The process for choosing the project lead should be described.
25+
- Who the project lead is should be indicated somewhere.
26+
- In the future, a GitHub issue should be created for election of each new maintainer.
27+
28+
### Points of Excellence
29+
30+
**The following aspects of governance are exemplary, and can be referenced as
31+
examples for other projects to copy:**
32+
33+
- Meeting notes are conveniently discoverable in GitHub at
34+
[Project-Meeting-Notes.md](https://github.com/k8gb-io/k8gb/blob/master/Project-Meeting-Notes.md),
35+
and recordings are quickly published to YouTube.
36+
37+
### Areas for Improvement
38+
39+
**Over the next year, the project should work on the following issues to improve
40+
its governance, these are considered non-blocking:**
41+
42+
- If there are people who make significant code contributions but not at the
43+
level of maintainers, consider an official "Contributor" role and listing to
44+
recognize and reward their contribution.
45+
46+
---
47+
48+
## Governance Summary
49+
50+
**The following review primarily consists of an audit on the project's
51+
self-assessment in their matriculation application.**
52+
53+
### Governance Evolution
54+
55+
**Governance has continuously been iterated upon by the project as a result of
56+
their experience applying it, with the governance history demonstrating
57+
evolution of maturity alongside the project's maturity evolution.**
58+
**Incubating:** Suggested | **Graduated:** Suggested
59+
60+
There has been little change to
61+
[GOVERNANCE](https://github.com/k8gb-io/k8gb/blob/master/GOVERNANCE.md) since it
62+
was written several years ago. [CODEOWNERS
63+
history](https://github.com/k8gb-io/k8gb/commits/master/CODEOWNERS) shows
64+
onboarding and offboarding of maintainers.
65+
66+
### Discoverability
67+
68+
**Clear and discoverable project governance documentation.**
69+
**Incubating:** Suggested | **Graduated:** Required
70+
71+
The project is all in one repo and that repo includes a
72+
[GOVERNANCE.md](https://github.com/k8gb-io/k8gb/blob/master/GOVERNANCE.md)
73+
document.
74+
75+
### Accuracy and Clarity
76+
77+
**Governance is up to date with actual project activities, including any
78+
meetings, elections, leadership, or approval processes.**
79+
**Incubating:** Suggested | **Graduated:** Required
80+
81+
Maintainers are listed in the repo's
82+
[CODEOWNERS](https://github.com/k8gb-io/k8gb/blob/master/CODEOWNERS) doc, and
83+
that document is actively updated when there are changes.
84+
85+
There is no record of an election accompanying the change.
86+
87+
Project meetings are held every other Wednesday as documented in
88+
[Project-Meeting-Notes.md](https://github.com/k8gb-io/k8gb/blob/master/Project-Meeting-Notes.md)
89+
and recordings and notes are published and linked there.
90+
91+
**Governance clearly documents [vendor-neutrality] of project direction.**
92+
**Incubating:** Suggested | **Graduated:** Required
93+
94+
Vendor neutrality is listed as a core principle of the project in
95+
[GOVERNANCE.md](https://github.com/k8gb-io/k8gb/blob/master/GOVERNANCE.md). The
96+
project does not appear to be packaged and/or supported by major vendors. It was
97+
originally created by [ABSA](https://www.absa.co.za/), a South African bank.
98+
99+
The project plans to move to a vendor-neutral API group in the future instead of
100+
`k8gb.absa.oss`, see <https://github.com/k8gb-io/k8gb/issues/2180>.
101+
102+
103+
### Decisions and Role Assignments
104+
105+
**Document how the project makes decisions on leadership roles, contribution
106+
acceptance, requests to the CNCF, and changes to governance or project goals.**
107+
**Incubating:** Suggested | **Graduated:** Required
108+
109+
The GOVERNANCE document states that all these decisions are made by a
110+
supermajority of maintainers, who are those listed in CODEOWNERS.
111+
112+
**Document how role, function-based members, or sub-teams are assigned,
113+
onboarded, and removed for specific teams (example: Security Response
114+
Committee).**
115+
**Incubating:** Suggested | **Graduated:** Required
116+
117+
There is only one group of project leaders, the maintainers listed in
118+
CODEOWNERS. According to the GOVERNANCE doc maintainers are added and removed by
119+
an election of a supermajority of current maintainers, but there is no record of
120+
previous elections.
121+
122+
There is no defined "contributor" role (other than maintainers), but all are
123+
welcomed to submit Pull Requests through GitHub.
124+
125+
There are no additional teams other than the maintainers.
126+
127+
### Maintainers and Maintainer Lifecycle
128+
129+
**Document a complete maintainer lifecycle process (including roles, onboarding,
130+
offboarding, and emeritus status).**
131+
**Incubating:** Suggested | **Graduated:** Required
132+
133+
Maintainers are added to CODEOWNERS following a period of contributions to the
134+
project. They are removed voluntarily or per a supermajority vote of
135+
maintainers.
136+
137+
**Demonstrate usage of the maintainer lifecycle with outcomes, either through
138+
the addition or replacement of maintainers as project events have required.**
139+
**Incubating:** Suggested | **Graduated:** Required
140+
141+
Examples of maintainers being onboarded and offboarded in the following commits:
142+
143+
- https://github.com/k8gb-io/k8gb/commit/1ecee28519f3a70ad4fe24ef5f47a6c93f2734d2
144+
- https://github.com/k8gb-io/k8gb/commit/9ab4528bfc103bbd4fbf580510491fd3386aed90
145+
- https://github.com/k8gb-io/k8gb/commit/c5ea88b4be8ee20a9698717f2f6204af86a45c2e
146+
- https://github.com/k8gb-io/k8gb/commit/5b35c35f5bfc643ffd180b82bfde6067b2fcaa79
147+
148+
**Document complete list of current maintainers, including names, contact
149+
information, domain of responsibility, and affiliation.**
150+
**Incubating:** Required | **Graduated:** Required
151+
152+
The project has no sub-projects.
153+
154+
**A number of active maintainers which is appropriate to the size and scope of
155+
the project.**
156+
**Incubating:** Required | **Graduated:** Required
157+
158+
There are 7 maintainers for the repo.
159+
160+
**Project maintainers from at least 2 organizations that demonstrates
161+
survivability.**
162+
**Incubating:** N/A | **Graduated:** Required
163+
164+
The maintainers work for 5 different organizations.
165+
166+
### Ownership
167+
168+
**Code and Doc ownership in Github and elsewhere matches documented governance
169+
roles.**
170+
**Incubating:** Required | **Graduated:** Required
171+
172+
Yes, governed by [CODEOWNERS](https://github.com/k8gb-io/k8gb/blob/master/CODEOWNERS).
173+
174+
### Code of Conduct
175+
176+
**Document adoption and adherence to the CNCF Code of Conduct or the project's
177+
CoC which is based off the CNCF CoC and not in conflict with it.**
178+
**Incubating:** Required | **Graduated:** Required
179+
180+
GOVERNANCE and
181+
[CODE_OF_CONDUCT](https://github.com/k8gb-io/k8gb/blob/master/CODE_OF_CONDUCT.md)
182+
documents refer to CNCF code of conduct.
183+
184+
**CNCF Code of Conduct is cross-linked from other governance documents.**
185+
**Incubating:** Required | **Graduated:** Required
186+
187+
GOVERNANCE and
188+
[CODE_OF_CONDUCT](https://github.com/k8gb-io/k8gb/blob/master/CODE_OF_CONDUCT.md)
189+
documents refer to CNCF code of conduct.
190+
191+
### Subprojects
192+
193+
**All subprojects, if any, are listed.**
194+
**Incubating:** Required | **Graduated:** Required
195+
196+
No subprojects.
197+
198+
**If the project has subprojects: subproject leadership, contribution, maturity
199+
status documented, including add/remove process.**
200+
**Incubating:** Suggested | **Graduated:** Required
201+
202+
Not applicable.
203+
204+
### Contributors and Community
205+
206+
**Contributor ladder with multiple roles for contributors.**
207+
**Incubating:** Suggested | **Graduated:** Suggested
208+
209+
No contributor ladder; only status available is full maintainer.
210+
211+
**Clearly defined and discoverable process to submit issues or changes.**
212+
**Incubating:** Required | **Graduated:** Required
213+
214+
Process follows typical GitHub workflow and is documented in
215+
[CONTRIBUTING.md](https://github.com/k8gb-io/k8gb/blob/master/CONTRIBUTING.md)
216+
217+
**Project must have, and document, at least one public communications channel
218+
for users and/or contributors.**
219+
**Incubating:** Required | **Graduated:** Required
220+
221+
Yes, see following question.
222+
223+
**List and document all project communication channels, including subprojects
224+
(mail list/slack/etc.). List any non-public communications channels and what
225+
their special purpose is.**
226+
**Incubating:** Required | **Graduated:** Required
227+
228+
Project has several public communications channels:
229+
- CNCF Slack: [#k8gb](https://cloud-native.slack.com/archives/C021P656HGB)
230+
- LinkedIn: <https://www.linkedin.com/company/k8gb/>
231+
- X: <https://x.com/k8gb_io>
232+
- Community meetings: <https://zoom-lfx.platform.linuxfoundation.org/meetings/k8gb>
233+
- Web site & blog: <http://k8gb.io/>
234+
235+
**Up-to-date public meeting schedulers and/or integration with CNCF calendar.**
236+
**Incubating:** Required | **Graduated:** Required
237+
238+
Biweekly public open community meetings are listed at
239+
<https://zoom-lfx.platform.linuxfoundation.org/meetings/k8gb>
240+
241+
**Documentation of how to contribute, with increasing detail as the project
242+
matures.**
243+
**Incubating:** Required | **Graduated:** Required
244+
245+
Project includes a
246+
[CONTRIBUTING.md](https://github.com/k8gb-io/k8gb/blob/master/CONTRIBUTING.md)
247+
doc with this info.
248+
249+
**Demonstrate contributor activity and recruitment.**
250+
**Incubating:** Required | **Graduated:** Required
251+
252+
See <https://insights.linuxfoundation.org/project/k8gb/contributors>
253+
254+
[project milestone or other requirement]: https://github.com/cncf/toc/tree/main/process#how-to-apply-to-move-levels
255+
[vendor-neutrality]: https://contribute.cncf.io/maintainers/community/vendor-neutrality/

0 commit comments

Comments
 (0)