consolidate community role definitions and election process#89
Merged
Conversation
- Introduce .gitvote.yml for automated voting on PRs - Set default voting duration to 2 weeks - Define pass threshold at 50% for votes - Specify allowed voters from specific teams and users - Enable periodic status checks and close on passing features Signed-off-by: mingcheng <mingcheng@apache.org>
- Update voting periods to fixed durations for consistency - Set nomination period to exactly 7 days for all roles - Clarify Approver and Maintainer voting period as 14 days - Add detailed steps for adding a new member with example Signed-off-by: mingcheng <mingcheng@apache.org>
- Introduce formal departure notice template in ISSUE_TEMPLATE - Update nomination process with clearer steps and templates - Refine voting thresholds and periods in COMMUNITY_MEMBERSHIP - Move assets to GitHub issue templates for better visibility - Clarify roles and responsibilities in governance documents Signed-off-by: mingcheng <mingcheng@apache.org> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
- Add expected behavior and reproduction steps in bug template - Create feature request template with use case section Signed-off-by: mingcheng <mingcheng@apache.org>
mingcheng
force-pushed
the
chroe/avoid-duplicate-definitions
branch
from
September 16, 2025 04:12
f7c9276 to
a2372fc
Compare
Contributor
There was a problem hiding this comment.
Pull Request Overview
This pull request consolidates and streamlines the community governance documentation by clarifying role definitions, election processes, and membership procedures across multiple files.
- Reorganized membership sections in COMMUNITY_MEMBERSHIP.md with dedicated subsections for each role
- Removed redundant "how to become" sections from COMMUNITY_LADDER.md to centralize process documentation
- Corrected file name capitalization inconsistencies (APPROVERS.md → Approvers.md, etc.)
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| GOVERNANCE.md | Added reference section linking to community membership and ladder documents |
| COMMUNITY_MEMBERSHIP.md | Restructured with separate role-specific sections and corrected file references |
| COMMUNITY_LADDER.md | Removed duplicate process documentation and corrected file name references |
Comments suppressed due to low confidence (1)
COMMUNITY_MEMBERSHIP.md:1
- Grammar error: should be 'A history of contributions for at least three months' to be grammatically correct.
# Dragonfly Community Membership
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
mingcheng
requested review from
chlins and
gaius-qi
and removed request for
bergwolf
September 16, 2025 04:13
- Update COMMUNITY_LADDER.md with clearer role qualifications - Streamline membership process in COMMUNITY_MEMBERSHIP.md - Correct file name capitalization for consistency - Consolidate election steps and voting criteria - Add detailed nomination and onboarding instructions Signed-off-by: mingcheng <mingcheng@apache.org>
mingcheng
force-pushed
the
chroe/avoid-duplicate-definitions
branch
from
September 16, 2025 04:15
a2372fc to
7e884ac
Compare
- Introduce voting process for unresolved Maintainer conflicts - Define simple majority rule for decision outcomes - Clarify abstention handling in voting process - Update COMMUNITY_MEMBERSHIP.md with new sections Signed-off-by: mingcheng <mingcheng@apache.org>
mingcheng
force-pushed
the
chroe/avoid-duplicate-definitions
branch
from
September 16, 2025 05:27
6bf8090 to
c49bea7
Compare
mingcheng
marked this pull request as ready for review
September 16, 2025 05:28
mingcheng
force-pushed
the
chroe/avoid-duplicate-definitions
branch
from
September 16, 2025 06:35
c49bea7 to
e43d110
Compare
mingcheng
added a commit
that referenced
this pull request
Sep 22, 2025
- Introduce .gitvote.yml for automated voting on PRs - Set default voting duration to 2 weeks - Define pass threshold at 50% for votes - Specify allowed voters from specific teams and users - Enable periodic status checks and close on passing features Signed-off-by: mingcheng <mingcheng@apache.org> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.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
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.
Description
Related Issue
dragonflyoss/dragonfly#4325