Governance: registry roles (contributors, operations, review board)

[davidpesce]

This defines the registry's standing roles and how someone takes one on: contributors (no privileges, open to anyone), registry operations (day-to-day pull-request and issue work under the public runbooks, GitHub triage access, index-changing acts prepared as pull requests the lead merges), and the review board (the code reviews behind the Reviewed tier, working through pull-request approvals rather than write access). Applications for the two standing roles are private (volunteer@camp-registry.org or a direct message to the lead) and never published; appointments are announced on acceptance.

Open for comment from anyone; the substance most worth poking at is the operations access model (triage plus acts-as-pull-requests), the review-board conflict rules, and the bars for admission. Adoption follows the comment period, with a design-decision entry recording it.

[davidherney]

Hola @davidpesce

I have a few questions.

1. "The lead"—is that you right now? How do we know who has each role? Because some actions, like "send a direct message to the lead," require explicitly knowing who holds it.

2. I don't see a procedure for appointing the leader. What happens if the current leader can no longer do it? What happens if the leader goes to the dark side? Do the others just have to clone themselves and continue on their own?

3. What does the leader need to verify their suitability? This isn't clear in the rules. Is it my profile on moodle.org or the Moodle Tracker? Or directly my GitHub profile? What information do we need to provide?

Is this okay, or should we discuss it in the CAMP Chat?

Saludos