Skip to content

Commit 5e3ad6a

Browse files
makahmadlukesneeringerrofrankeltoumorokoshi
authored
chore: Initial AIP governance (#115)
Clarifying governance help define roles and responsibilities of current members, and clarifies how one can get more involved. --------- Co-authored-by: Luke Sneeringer <luke@sneeringer.com> Co-authored-by: Richard Frankel <richard@frankel.tv> Co-authored-by: Yusuke Tsutsumi <yusuke@tsutsumi.io>
1 parent e30773a commit 5e3ad6a

1 file changed

Lines changed: 75 additions & 0 deletions

File tree

GOVERNANCE.md

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
# API Improvement Proposals: Project Charter
2+
3+
## Article I: Purpose
4+
5+
1. The API Improvement Proposals (AIP) project exists to help developers and
6+
organizations build clear, consistent network APIs and clients by providing
7+
an extensible set of design guidelines (AIPs) and an ecosystem of tools to
8+
apply those rules in practice.
9+
2. To support this aim, the project provides and maintains tools that enrich
10+
the experience of developing and using APIs that conform to the project's
11+
design guidelines by generating artifacts such as client libraries and
12+
documentation.
13+
14+
## Article II: Association
15+
16+
1. The AIP project is a project of the Cloud Native Computing Foundation. As
17+
such, it accepts the [CNCF Code of Conduct][0].
18+
19+
## Article III: Steering Committee
20+
21+
1. The AIP project shall be governed by a steering committee, comprising at
22+
least five representatives from at least five distinct organizations.
23+
2. No more than one third of the committee shall represent or be employed by
24+
the same organization.
25+
1. In the event that ambiguities arise regarding what constitutes "the same
26+
organization," a vote of the committee shall decide. Any members from the
27+
organizations under consideration may deliberate, but shall recuse
28+
themselves from the vote.
29+
3. Membership on the steering committee shall be by invitation of the current
30+
steering committee. The steering committee shall meet at least once annually
31+
to consider the addition, removal, or replacement of members.
32+
4. The members of the steering committee shall be maintained in a
33+
MAINTAINERS.md file in the
34+
[primary AIP GitHub repository](https://github.com/aip-dev/aip).
35+
5. Steering committee members accept the following responsibilities:
36+
1. Ownership of the charter, vision, and direction of the AIP project.
37+
2. Regular attendance and participation at stated committee meetings.
38+
3. Contribution of design guidance or code as appropriate, and reviewing the
39+
contributions of others.
40+
6. Steering committee members who are unable or unwilling to continue to
41+
perform the responsibilities described above may voluntarily step down from
42+
the committee or may be removed from the steering committee without
43+
prejudice. Former committee members will be designated as "emeritus" in the
44+
maintainers list.
45+
7. The steering committee may appoint additional maintainers, to whom it may
46+
delegate tasks as necessary.
47+
48+
## Article IV: Source of Truth
49+
50+
1. The AIP GitHub repositories are the source of truth for everything in the
51+
project, including both code and guidelines.
52+
53+
## Article V: Meetings & Voting
54+
55+
1. The steering committee shall hold a regular meeting on a cadence of its
56+
choosing, and shall keep minutes of said meetings in a GitHub repository set
57+
aside for that purpose, which shall be accessible by all steering committee
58+
members.
59+
1. Meetings and minutes may be public or private, at the discretion of the
60+
steering committee.
61+
2. The steering committee ordinarily operates by consensus, and recording votes
62+
for each decision is not required (but the decision should be recorded in
63+
the minutes). When possible, decisions and voting shall be done using GitHub
64+
issues for transparency.
65+
3. In the event that a vote is required, an email shall be sent to each
66+
steering committee explaining the issue in question and allowing at least 10
67+
business days for voting. The specifics of how elections are handled are at
68+
the discretion of the steering committee.
69+
70+
## Article VI: Amendment
71+
72+
This charter may be amended by a two-thirds supermajority of the steering
73+
committee, after conducting an vote as described in V§3.
74+
75+
[0]: https://github.com/cncf/foundation/blob/master/code-of-conduct.md

0 commit comments

Comments
 (0)