Add core maintainer section in contributor ladder. #222
Conversation
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
xuezhaojun
changed the title
xuezhaojun
force-pushed
the
fix/unify-contributor-ladder-governance
branch
from
4930a8b to
defd3d5
Compare
qiujian16
reviewed
Aug 11, 2025
CONTRIBUTOR_LADDER.md
Outdated
| * Mentor and guide the development of other maintainers | ||
|
|
||
| Process of becoming a Core Maintainer: | ||
| 1. Any current Core Maintainer or Steering Committee member may nominate a current Maintainer to become a Core Maintainer. |
Member
There was a problem hiding this comment.
let's remove mention of Steering Committee member for now
qiujian16
reviewed
Aug 11, 2025
CONTRIBUTOR_LADDER.md
Outdated
| 2. The nomination should include evidence of exceptional contributions to core functionality and leadership within the project. | ||
| 3. The nominee will add a comment testifying that they agree to all requirements of becoming a Core Maintainer. | ||
| 4. A majority of the current Core Maintainers must approve the nomination. | ||
| 5. The Steering Committee will review and confirm the appointment. |
- Add Core Maintainer role definition to CONTRIBUTOR_LADDER.md to match GOVERNANCE.md - Standardize terminology to use 'Organization Member' consistently across both documents - Align role descriptions, requirements, and privileges between the two files - Update advancement requirements to be consistent (3+ months for Organization Member) - Complete TODO item for election voting privileges - Remove Steering Committee references from Core Maintainer advancement process - Ensure all contributor ladder roles have consistent definitions and processes This change resolves inconsistencies between the governance document and contributor ladder, providing clear and unified guidance for community members. Signed-off-by: xuezhaojun <[email protected]>
xuezhaojun
force-pushed
the
fix/unify-contributor-ladder-governance
branch
from
defd3d5 to
5fbb43b
Compare
Member
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mikeshng, qiujian16, xuezhaojun The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-merge-bot
bot
merged commit 4c9e5e9
into
open-cluster-management-io:main
2 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary
This PR resolves inconsistencies between
GOVERNANCE.mdandCONTRIBUTOR_LADDER.mdregarding contributor roles and definitions.Changes Made
🎯 Core Maintainer Role Addition
CONTRIBUTOR_LADDER.mdto matchGOVERNANCE.md🔄 Terminology Standardization
📋 Role Description Alignment
⚡ Process Improvements
Impact
Testing
/assign @qiujian16