Governance & Meritocracy Guidelines
AMEVA 재단 운영 규정 및 메리토크라시 헌장
Meritocracy Principle
AOSF operates on the principle that "code and demonstrable contributions speak louder than corporate affiliation or titles." Authority is earned through sustained technical contributions, rigorous code reviews, and transparent community stewardship.
1. Organizational Hierarchy
| Role | Qualification | Core Responsibilities & Privileges |
|---|---|---|
| Board of Directors | Foundational Leadership | Strategic governance, legal oversight, trademark stewardship. Chair: Eunho Kim (@uno-km). |
| Project Management Committee (PMC) | Elected Key Maintainers | Technical roadmap approval, package release authorization (PyPI/npm), committer nominations. |
| Committers | Active Regular Contributors | Direct write access to project repositories, PR reviews, bug triage. |
| Contributors & Users | Global Community | Issue reporting, feature requests, patch submissions, documentation improvements. |
2. Decision-Making & Voting Protocol
All formal decisions follow standard open-source consensus voting:
- +1 (Approval): Agreement with the proposal.
- 0 (Abstain): Neutral or no opinion.
- -1 (Veto): Clear objection. Must be accompanied by technical justification and an alternative proposal.
| Action Type | Minimum Requirement | Veto Impact |
|---|---|---|
| Code PR Merge | At least one +1 from a Committer | -1 halts merge until technical consensus is reached |
| Package Release (PyPI/npm) | At least three +1s from PMC members | Majority rules (+1 > -1) after 72-hour window |
| New Committer Election | At least three +1s from PMC members | Consensus with zero vetoes |
| TLP Graduation | 2/3 majority vote of Board & PMC | Final ratification by Board of Directors |
3. Quality & Verification Gates
Before any package is tagged or published, it must pass 4 verification gates:
- Automated CI/CD suite with 100% PASS on all unit and integration tests.
- Single-Source Op Contract verification without broken dependencies.
- Zero unverified claims or lint errors in documentation.
- Successful reproducible build in an isolated clean environment.