Skip to content

docs(governance): Update subproject governance documentation 📝 #146

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
gaius-qi merged 1 commit into from
Mar 3, 2026
Merged

docs(governance): Update subproject governance documentation 📝 #146

Show file tree
Hide file tree
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
4 changes: 0 additions & 4 deletions GOVERNANCE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,10 +13,6 @@ Welcome to the Dragonfly project's governance guide! We believe in open and tran

This governance document applies to the Dragonfly project and all its subprojects or libraries, including but not limited to [Nydus](https://github.com/dragonflyoss/nydus), nydus-snapshotter, api, docs, console, and client.

These subprojects and libraries may have their own maintainers and contributors, but they all adhere to the overarching principles and practices established by the Dragonfly community.

Note: Due to the smaller scale of these subprojects and libraries, some governance processes and roles may be simplified.

For more about our subprojects governance, please refer to the [Subprojects Governance](SUBPROJECTS.md) document.

## Roles and Responsibilities
Expand Down
2 changes: 2 additions & 0 deletions SUBPROJECTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@ Dragonfly subprojects extend the core functionality of the ecosystem and follow

Subprojects adhere to the same community standards as the main project but may have simplified governance processes due to their smaller scale, such as combined roles or streamlined decision-making.

Once contributors to subprojects are promoted through the community ladder (see [COMMUNITY_MEMBERSHIP.md](COMMUNITY_MEMBERSHIP.md) and [COMMUNITY_LADDER.md](COMMUNITY_LADDER.md)), their names are uniformly updated in the central [roles](roles/) directory.

For detailed governance information, see [GOVERNANCE.md](GOVERNANCE.md) and [COMMUNITY_MEMBERSHIP.md](COMMUNITY_MEMBERSHIP.md).

## Status
Expand Down
8 changes: 1 addition & 7 deletions roles/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,10 +20,4 @@ You can find the list of all security team members in the [Security-Team.md](Sec

## Subprojects

The community has several subprojects, each with its own maintainers and contributors. [According the governance model](../GOVERNANCE.md#scope), subprojects adhere to the same governance principles as the main project but may simplify some governance processes and roles due to their smaller scale.

### Nydus

#### Maintainers {#nydus-maintainers}

You can find the list of all maintainers in the [Nydus-Maintainers.md](https://github.com/dragonflyoss/nydus/blob/master/MAINTAINERS.md).
The community has several subprojects. Once contributors of subprojects pass the proper promotion processes (e.g., becoming a Member, Approver, or Maintainer), their names are uniformly updated and managed in the corresponding roles lists in this directory, rather than being dispersed throughout individual subproject repositories.