From f1faa7f98b3feb1525ceee8bb96fd8aee2bcfc8b Mon Sep 17 00:00:00 2001 From: mingcheng Date: Tue, 3 Mar 2026 15:28:34 +0800 Subject: [PATCH] =?UTF-8?q?docs(governance):=20Update=20subproject=20gover?= =?UTF-8?q?nance=20documentation=20=F0=9F=93=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Clarify governance principles for Dragonfly subprojects - Update references to role management and documentation locations - Emphasize simplified processes for smaller subprojects Signed-off-by: mingcheng --- GOVERNANCE.md | 4 ---- SUBPROJECTS.md | 2 ++ roles/README.md | 8 +------- 3 files changed, 3 insertions(+), 11 deletions(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 185b227..d5bf89f 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -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 diff --git a/SUBPROJECTS.md b/SUBPROJECTS.md index 68a9f75..3e8214e 100644 --- a/SUBPROJECTS.md +++ b/SUBPROJECTS.md @@ -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 diff --git a/roles/README.md b/roles/README.md index 689c807..7aacee1 100644 --- a/roles/README.md +++ b/roles/README.md @@ -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.