Skip to content

docs(steering): formalize SC membership application process - #156

Open
yada wants to merge 1 commit into
mainfrom
yada/SC-charter-update
Open

yada wants to merge 1 commit into
mainfrom
yada/SC-charter-update

Conversation

@yada

@yada yada commented Oct 27, 2026

Copy link
Copy Markdown
Member

Summary

Formalizes the Steering Committee membership application process, as agreed at the first SC meeting
(minutes) and requested in #126. Unblocks the pending applications #119 and #121.

Changes

  • STEERING.md
    • Add Composition and Representation (adopter and contributor seats).
    • Replace invitation-only and two-nominator with a hybrid self-application and invitation model.
    • Define the application (GitHub issue, steering label, required information, confirmation of the charter and CoC) and review: 14-day vote, candidate doesn't vote, conflicts disclosed.
    • Voting: SC members and maintainers, org-balanced per GOVERNANCE.md, approval by 2/3 of all eligible votes rounded up.
    • Remove the ranked-vote and tie-break rules and the "3 or fewer take seats without vote" shortcut.
    • Align charter-change approval with GOVERNANCE.md (org-balanced vote plus SC majority).
    • Public by default, private escalation for sensitive cases, results archived on the tracking issue.
  • .gitvote.yml: add maintainers as binding voters on the sc profile only. default is unchanged.

Notes

  • The git-vote tally is headcount-based and indicative. The org-balanced result is recorded in the issue, as GOVERNANCE.md requires.
  • Approval: formal /vote (maintainers, org-balanced) plus an SC majority.

After merge

Open /vote-sc for #119 and #121 once each applicant confirms the charter, the CoC and meeting attendance.

Fixes #126

Replace the invitation-only, two-nominator model with a hybrid
self-application/invitation process, and align voting with GOVERNANCE.md.

- Add Composition and Representation (adopter/contributor seats)
- Define how to apply (GitHub issue with `steering` label, required info)
- Define review and selection: 14-day vote, org-balanced voting,
  2/3 of all eligible votes rounded up, candidate does not vote
- Remove the two-nominator, ranked-vote and tie-break rules
- Align charter change approval with GOVERNANCE.md
- Add public-by-default discussion with a private escalation exception
- .gitvote.yml: add maintainers as binding voters for /vote-sc

Fixes #126

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: Yacine Kheddache <yacine@microcks.io>
@yada yada added the steering Microcks Steering Committee related topic. label Oct 27, 2026
@yada

yada commented Oct 27, 2026

Copy link
Copy Markdown
Member Author

@microcks/steering-committee: the proposed update to the SC charter is ready for review. It formalizes the membership application process (#126) and unblocks the two pending applications (#119, #121).

What changes (details in the PR description):

  • Hybrid self-application and invitation model, via a GitHub issue with the steering label
  • 14-day vote by SC members and maintainers, org-balanced per GOVERNANCE.md, with approval by 2/3 of all eligible votes rounded up
  • The old two-nominator, ranked-vote and tie-break rules are removed
  • .gitvote.yml: maintainers become binding voters on /vote-sc

What we need from you: please review the changes and approve this PR (or comment with change requests) so we can record a majority of SC members. Per the updated charter, it also requires a formal org-balanced maintainer vote, which I'll open with /vote once the SC feedback is in.

Please respond within 7 days if possible, so we can move forward with the two pending applications. Thanks! 🙏

@ludovic-pourrat

Copy link
Copy Markdown

Works for me.

1 similar comment
@kinlane

kinlane commented Nov 5, 2026

Copy link
Copy Markdown

Works for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

steering Microcks Steering Committee related topic.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarify and Formalize Steering Committee Membership Application Process

3 participants