Skip to content

Clarify governance blog #234

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tombentley merged 1 commit into from
Mar 5, 2026
Merged

Clarify governance blog #234

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions _posts/2026-03-05-evolving-governance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,9 @@ It creates a clearer pathway for contributors to take on leadership roles based

These changes are already reflected in our updated [`GOVERNANCE.md`](https://github.com/kroxylicious/.github/blob/main/GOVERNANCE.md).

The initial [`COMMITTERS.md`](https://github.com/kroxylicious/.github/blob/main/COMMITTERS.md) and [`PMs.md`](https://github.com/kroxylicious/.github/blob/main/PMs.md) are the same people who were previously code owners and project admins.
This revised governance model has not changed anyone's access.

## Moving Beyond `CODEOWNERS`

We are also moving away from using the GitHub `CODEOWNERS` file to enforce directory-level restrictions.
Expand Down