Governance and membership for Cloud Native Karachi, a CNCF Cloud Native Community Group.
This repository is the register of record. Roles belong to people listed in files here, changes happen by pull request, and git history is the audit trail.
The website is in cloud-native-karachi.github.io. Registration and attendance live on our group page, which is the CNCF's record, not this repository.
To attend a meetup you do not need this repository. Register on the group page, join WhatsApp, turn up. That makes you a Participant, and it is a complete way to be part of the group.
Read on if you want to help run it.
flowchart LR
P["Participant<br/><small>register and show up</small>"]
M["Member<br/><small>3 units, 2 events, 2 sponsors</small>"]
L["SIG Lead<br/><small>2 SIG activities</small>"]
O["Organizer<br/><small>2 events owned, LFC102, CNCF approval</small>"]
E["Emeritus"]
P --> M --> L --> O
M --> O
M -. "inactive 12 months" .-> E
O -. "steps down or term ends" .-> E
| Role | Listed in | Who decides | Detail |
|---|---|---|---|
| Participant | Nowhere, no application | Nobody, it is open | membership.md |
| Member | members/members.yaml | 2 sponsors, 1 organizer approves | membership.md |
| SIG Lead | The SIG's charter | Majority of organizers | sigs.md |
| Organizer | members/organizers.yaml plus the CNCF group page | Organizers nominate, CNCF appoints | organizers.md |
| Emeritus | members/emeritus.yaml | Automatic or on request | membership.md |
Organizer is the only role the group cannot grant. See the CNCF request.
A SIG is a standing group with one topic, a charter, and something scheduled every quarter. It stays proposed until it has a lead and a date for its first activity, and only then is it announced as joinable.
sigs/README.md is the index and carries the topic, state and lead of each one. Rules and lifecycle: governance/sigs.md.
| I want to | Do this |
|---|---|
| Become a Member | Open a membership request |
| Speak at a meetup | Open a talk proposal |
| Start a SIG | governance/sigs.md, then a SIG proposal |
| Nominate an organizer | governance/organizers.md |
| Host or sponsor a meetup | events/playbook.md |
| Report a Code of Conduct concern | CODE_OF_CONDUCT.md |
governance/ roles, criteria, decision making, moderation
members/ the register, validated in CI
sigs/ one directory per SIG, each with a charter
events/ running a meetup, selecting talks
scripts/ register validation
Membership thresholds follow the phase field in members.yaml. While it reads founding, the lower bar in the founding phase applies. That phase ends once the group has held 3 events and listed 10 Members, both of them, and scripts/validate_members.py prints the counts and the phase on every pull request.
Headcounts are not repeated in prose here. Who holds a role is whatever organizers.yaml, members.yaml and emeritus.yaml say, and registration and attendance stay on the group page.
CC BY 4.0 for documentation, Apache 2.0 for scripts.