feat(governance): split technical authority into subproject committees - #71
Draft
gbartolini wants to merge 1 commit into
Draft
feat(governance): split technical authority into subproject committees#71gbartolini wants to merge 1 commit into
gbartolini wants to merge 1 commit into
Conversation
gbartolini
marked this pull request as draft
July 15, 2026 03:57
gbartolini
force-pushed
the
dev/67
branch
29 times, most recently
from
July 20, 2026 04:35
b9fb316 to
11cedd0
Compare
gbartolini
force-pushed
the
dev/67
branch
2 times, most recently
from
July 22, 2026 02:05
5cdbab7 to
c53e62d
Compare
gbartolini
force-pushed
the
dev/67
branch
2 times, most recently
from
September 8, 2026 15:20
b57cf47 to
2541f11
Compare
gbartolini
changed the title
gbartolini
force-pushed
the
dev/67
branch
23 times, most recently
from
September 9, 2026 14:31
c4a09c9 to
6529e42
Compare
Reorganise CloudNativePG into four subprojects (Core, Supply Chain, Community/Docs & Ecosystem, Extensibility), each with its own self-selecting maintainer committee holding technical authority over its components, listed in the new `subprojects/` folder. Introduce the Component Owner / Subproject Maintainer contributor ladder (`CONTRIBUTOR_LADDER.md`) that feeds those committees, replacing the flat Maintainer/Component Owner model. The Steering Committee is, for now, simply the existing group of CloudNativePG Maintainers listed in `MAINTAINERS.md`, deciding under the same per-person voting rules already in use (lazy consensus, falling back to simple majority, two-thirds for changes to this document). It takes on project-wide governance duties that don't fit any one subproject: the CNCF interface, adding/removing subprojects, Code of Conduct committee oversight, security response coordination, and infrastructure administration. Also name and define the Infrastructure Team, to whom Steering delegates day-to-day infrastructure administration (GitHub org admin, CI/CD secrets, cloud accounts): the existing `admins` GitHub team, added to and removed from by Steering the same way as its other business. It is a distinct body from the Steering Committee, even though membership is identical today. This does not yet touch org-balanced voting, a per-organisation seat cap, or Steering elections; those remain a follow-up change. Closes #67 Refs #69 Assisted-by: Claude Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Reorganise CloudNativePG into four subprojects (Core, Supply Chain, Community/Docs & Ecosystem, Extensibility), each with its own self-selecting maintainer committee holding technical authority over its components, listed in the new
subprojects/folder. Introduce the Component Owner / Subproject Maintainer contributor ladder (CONTRIBUTOR_LADDER.md) that feeds those committees, replacing the flat Maintainer/Component Owner model.The Steering Committee is, for now, simply the existing group of CloudNativePG Maintainers listed in
MAINTAINERS.md, deciding under the same per-person voting rules already in use (lazy consensus, falling back to simple majority, two-thirds for changes to this document). It takes on project-wide governance duties that don't fit any one subproject: the CNCF interface, adding/removing subprojects, Code of Conduct committee oversight, security response coordination, and infrastructure administration.Also name and define the Infrastructure Team, to whom Steering delegates day-to-day infrastructure administration (GitHub org admin, CI/CD secrets, cloud accounts): the existing
adminsGitHub team, added to and removed from by Steering the same way as its other business. It is a distinct body from the Steering Committee, even though membership is identical today.This does not yet touch org-balanced voting, a per-organisation seat cap, or Steering elections; those remain a follow-up change.
Closes #67
Refs #69
Assisted-by: Claude