docs: update community roles and responsibilities (#104)

gaius-qi · web-flow · commit 6ed62561ed23 · 2025-09-22T19:36:54.000+08:00
Signed-off-by: Gaius &lt;gaius.qi@gmail.com&gt;
diff --git a/COMMUNITY_LADDER.md b/COMMUNITY_LADDER.md
@@ -91,10 +91,12 @@ As the project grows, these roles and responsibilities might change. The final s
 A **Contributor** is anyone who adds value to the project. This can be through code, but it doesn't have to be! This role is often where new or occasional contributors start.
 
 - **Responsibilities**:
+
   - Follow the project's [Code of Conduct](CODE_OF_CONDUCT.md).
   - Stick to the [Contribution Guide](CONTRIBUTING.md).
 
 - **Qualifications**:
+
   - Open to anyone who wants to be part of the community.
   - Contributions can include things like:
     - Joining in on community discussions.
@@ -116,10 +118,12 @@ This is the first step to becoming a Member.
 A **Member** is a consistent contributor who is actively involved in the project. They have more permissions in our repositories and are trusted to act in the community's best interest.
 
 - **Responsibilities**:
+
   - Make regular contributions to the project.
   - Finish any tasks or initiatives you volunteer for.
 
 - **Qualifications**:
+
   - A history of successful contributions, including at least one of these:
     - Submitting or reviewing PRs.
     - Fixing issues or bugs.
@@ -141,13 +145,15 @@ The current Member list is maintained in the [MEMBERS.md](roles/Members.md) file
 An **Approver** is a Member who takes ownership of a specific part of the project (like code, docs, or tests). They play a key role in keeping our quality high by reviewing and approving changes in their area.
 
 - **Responsibilities**:
+
   - Handle all the responsibilities of a Member.
   - Regularly review PRs in your area of expertise.
   - Make sure changes meet our coding standards, don't introduce bugs, and are good for the project.
   - Help other contributors become Approvers.
   - Help triage issues.
 
 - **Qualifications**:
+
   - You must already be a Member.
   - Proven track record of high-quality reviews and contributions.
   - Deep understanding of your specific area.
@@ -165,6 +171,7 @@ The current Approver list is maintained in the [Approvers.md](roles/Approvers.md
 A **Maintainer** is a highly trusted member of the project with the authority to merge code, vote on project matters, and help guide the project's direction. This role is for those who have shown a deep commitment to our community.
 
 - **Responsibilities**:
+
   - Fulfill all the responsibilities of an Approver.
   - Merge PRs to the main branch.
   - Maintain the codebase's overall quality, stability, and performance.
@@ -176,6 +183,7 @@ A **Maintainer** is a highly trusted member of the project with the authority to
   - Approve promotions to various roles within the project.
 
 - **Qualifications**:
+
   - The specifics are detailed in our project's [governance document](./GOVERNANCE.md) under the commit access criteria.
   - A history of long-term, high-quality contributions and leadership.
   - In-depth understanding of the project’s architecture and design.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -70,51 +70,51 @@ To submit a PR, you'll need a GitHub account. Once you have one, follow these st
 
 1. **FORK** Dragonfly to your own repository.
 
-    To do this, just click the "Fork" button in the top-right corner of the [dragonflyoss/dragonfly](https://github.com/dragonflyoss/dragonfly) main page. This will create a copy of the repository under your own account at `https://github.com/<your-username>/dragonfly`.
+   To do this, just click the "Fork" button in the top-right corner of the [dragonflyoss/dragonfly](https://github.com/dragonflyoss/dragonfly) main page. This will create a copy of the repository under your own account at `https://github.com/<your-username>/dragonfly`.
 
 2. **CLONE** your forked repository to your local machine.
 
-    Use `git clone --recurse-submodules https://github.com/<your-username>/dragonfly.git` to clone the repository locally. Now you can create new branches and make your changes.
+   Use `git clone --recurse-submodules https://github.com/<your-username>/dragonfly.git` to clone the repository locally. Now you can create new branches and make your changes.
 
 3. **Set the remote upstream** to `https://github.com/dragonflyoss/dragonfly.git`.
 
-    Run these two commands:
+   Run these two commands:
 
-    ```bash
-    git remote add upstream https://github.com/dragonflyoss/dragonfly.git
-    git remote set-url --push upstream no-pushing
-    ```
+   ```bash
+   git remote add upstream https://github.com/dragonflyoss/dragonfly.git
+   git remote set-url --push upstream no-pushing
+   ```
 
-    With this remote setup, your git remote configuration should look like this:
+   With this remote setup, your git remote configuration should look like this:
 
-    ```bash
-    $ git remote -v
-    origin     https://github.com/<your-username>/dragonfly.git (fetch)
-    origin     https://github.com/<your-username>/dragonfly.git (push)
-    upstream   https://github.com/dragonflyoss/dragonfly.git (fetch)
-    upstream   no-pushing (push)
-    ```
+   ```bash
+   $ git remote -v
+   origin     https://github.com/<your-username>/dragonfly.git (fetch)
+   origin     https://github.com/<your-username>/dragonfly.git (push)
+   upstream   https://github.com/dragonflyoss/dragonfly.git (fetch)
+   upstream   no-pushing (push)
+   ```
 
-    This setup makes it easy to keep your local branches in sync with the main project.
+   This setup makes it easy to keep your local branches in sync with the main project.
 
 4. **Create a branch** to add a new feature or fix an issue.
 
-    First, update your local working directory:
+   First, update your local working directory:
 
-    ```bash
-    cd dragonfly
-    git fetch upstream
-    git checkout main
-    git rebase upstream/main
-    ```
+   ```bash
+   cd dragonfly
+   git fetch upstream
+   git checkout main
+   git rebase upstream/main
+   ```
 
-    Then, create a new branch for your work:
+   Then, create a new branch for your work:
 
-    ```bash
-    git checkout -b <new-branch>
-    ```
+   ```bash
+   git checkout -b <new-branch>
+   ```
 
-    Now you can make your changes on the `new-branch`, then build and test your code.
+   Now you can make your changes on the `new-branch`, then build and test your code.
 
 ### Branching Strategy
 
diff --git a/GOVERNANCE.md b/GOVERNANCE.md
@@ -40,16 +40,3 @@ Any major changes to this governance document will be discussed among the Mainta
 ## Security Reporting
 
 Security is a top priority for us. If you find a security vulnerability, please check our [Dragonfly Security Reporting guide](SECURITY.md) for instructions on how to report it responsibly.
-
-## Contact
-
-Join the conversation and become a part of our community!
-
-- **Slack**: Chat with us on the [#dragonfly](https://cloud-native.slack.com/messages/dragonfly/) channel in the [CNCF Slack](https://slack.cncf.io/).
-- **GitHub Discussions**: Have questions or ideas? Join the [Dragonfly Discussion Forum](https://github.com/dragonflyoss/dragonfly/discussions).
-- **Developer Group**: <dragonfly-developers@googlegroups.com>
-- **Maintainer Group**: <dragonfly-maintainers@googlegroups.com>
-- **Twitter**: Follow us at [@dragonfly_oss](https://twitter.com/dragonfly_oss).
-- **DingTalk**: [22880028764](https://qr.dingtalk.com/action/joingroup?code=v1,k1,pkV9IbsSyDusFQdByPSK3HfCG61ZCLeb8b/lpQ3uUqI=&_dt_no_comment=1&origin=11)
-
-This document provides a clear framework for the healthy growth of the Dragonfly project. As our community and project evolve, we may update it from time to time.
diff --git a/releases/2.3.0/README.md b/releases/2.3.0/README.md
@@ -1,6 +1,6 @@
-# Dragonfly v2.3.0 is released!
+# Dragonfly v2.3.0 is released
 
-Dragonfly v2.3.0 is released! 🎉🎉🎉 Thanks the [contributors](https://github.com/dragonflyoss/dragonfly/graphs/contributors) who made this release happend and welcome you to visit [d7y.io](https://d7y.io) website.
+Dragonfly v2.3.0 is released!🎉🎉🎉 Thanks the [contributors](https://github.com/dragonflyoss/dragonfly/graphs/contributors) who made this release happend and welcome you to visit [d7y.io](https://d7y.io) website.
 
 ![dragonfly](images/dragonfly-linear.png)
 
@@ -20,7 +20,7 @@ $ dfcache import /tmp/file.txt
 ```
 
 ```shell
-$ dfcache export 2229733261 -O /tmp/file.txt
+dfcache export 2229733261 -O /tmp/file.txt
 ```
 
 ![p2](images/p2.webp)
@@ -141,6 +141,7 @@ For detailed information on the specific security issues addressed and the corre
 ## Nydus
 
 ### New features and enhancements
+
 - nydusify copy: support chunked upload and retry mechanisms to handle large image blobs.
 - nydusify check: refactor to support OCI v1 and nydus format images as both source and target.
 - nydusd: support chunk-level CRC data validation for image data consistency.
diff --git a/roles/Members.md b/roles/Members.md
@@ -6,8 +6,8 @@ This document lists all current members of the Dragonfly community, along with t
 
 <!-- markdownlint-disable -->
 
-| GitHub ID | Name  | Email | Company or Organization |
-| :-------: | :---: | :---: | :---------------------: |
+|               GitHub ID               |     Name      |        Email         |           Company or Organization            |
+| :-----------------------------------: | :-----------: | :------------------: | :------------------------------------------: |
 | [Zephyr](https://github.com/Zephyrcf) | Changfu Zhang | zinsist777@gmail.com | University of Science and Technology Beijing |
 
 <!-- markdownlint-restore -->
@@ -18,7 +18,7 @@ Below is the list of emeritus (retired) members. Thank them for their contributi
 
 <!-- markdownlint-disable -->
 
-| GitHub ID | Name  | Email | Company or Organization |
-| :-------: | :---: | :---: | :---------------------: |
+| GitHub ID | Name | Email | Company or Organization |
+| :-------: | :--: | :---: | :---------------------: |
 
 <!-- markdownlint-restore -->
diff --git a/roles/README.md b/roles/README.md
@@ -1,44 +1,29 @@
-# Dragonfly Community Roles
+# Community Roles
 
 This directory contains information about the various roles and membership levels within the Dragonfly community. Our community follows a structured approach to governance and participation, with different levels of responsibility and access.
 
-## Role Definitions
+## Members
 
-The Dragonfly community has several membership levels, each with specific responsibilities and privileges:
+You can find the list of all members in the [Members.md](Members.md).
 
-### [Members](Members.md)
+## Approvers
 
-Community members who have made sustained contributions to the project and are committed to its continued development.
+You can find the list of all approvers in the [Approvers.md](Approvers.md).
 
-### [Approvers](Approvers.md)
+## Maintainers
 
-Contributors who have the ability to approve pull requests and are responsible for maintaining code quality in specific areas.
+You can find the list of all maintainers in the [Maintainers.md](Maintainers.md).
 
-### [Maintainers](Maintainers.md)
+## Security Team
 
-Senior contributors who have overall responsibility for the project direction, architecture decisions, and community governance.
-
-### [Security Team](Security-Team.md)
-
-Dedicated team members responsible for handling security issues, vulnerability reports, and security-related communications.
+You can find the list of all security team members in the [Security-Team.md](Security-Team.md).
 
 ## Subprojects
 
-The Dragonfly 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.
-
-### Maintainers
-
-- [nydus](https://github.com/dragonflyoss/nydus) maintainers are located in the [nydus repository](https://github.com/dragonflyoss/nydus/blob/master/MAINTAINERS.md).
-
-## Getting Involved
-
-If you're interested in contributing to Dragonfly and potentially taking on a community role, please:
+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.
 
-1. Start by reading our [Community Membership](../COMMUNITY_MEMBERSHIP.md) guidelines
-2. Review the [Community Ladder](../COMMUNITY_LADDER.md) to understand progression paths
-3. Check out our [Contributing Guidelines](../CONTRIBUTING.md)
-4. Join our community discussions and start contributing!
+### Nydus
 
-## Governance
+#### Maintainers {#nydus-maintainers}
 
-For information about how decisions are made in the Dragonfly community, please refer to our [Governance](../GOVERNANCE.md) document.
+You can find the list of all maintainers in the [Nydus-Maintainers.md](https://github.com/dragonflyoss/nydus/blob/master/MAINTAINERS.md).
