Skip to content

Commit 83f7194

Browse files
sabre1041sabre1041
committed
Initial project governance
Signed-off-by: Andrew Block <andy.block@gmail.com>
1 parent 174e70b commit 83f7194

2 files changed

Lines changed: 124 additions & 8 deletions

File tree

‎GOVERNANCE.md‎

Lines changed: 120 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,120 @@
1+
# SOPS Project Governance
2+
3+
The SOPS project is dedicated to enabling the management of encrypted files in a variety of formals through a range of supported encryption backends.
4+
5+
- [Values](#values)
6+
- [Maintainers](#maintainers)
7+
- [Becoming a Maintainer](#becoming-a-maintainer)
8+
- [CNCF Resources](#cncf-resources)
9+
- [Code of Conduct Enforcement](#code-of-conduct)
10+
- [Security Response Team](#security-response-team)
11+
- [Voting](#voting)
12+
- [Modifications](#modifying-this-charter)
13+
14+
## Values
15+
16+
The SOPS project and its leadership embrace the following values:
17+
18+
* Openness: Communication and decision-making happens in the open and is discoverable for future
19+
reference. As much as possible, all discussions and work take place in public
20+
forums and open repositories.
21+
22+
* Fairness: All stakeholders have the opportunity to provide feedback and submit
23+
contributions, which will be considered on their merits.
24+
25+
* Community over Product or Company: Sustaining and growing our community takes
26+
priority over shipping code or sponsors' organizational goals. Each
27+
contributor participates in the project as an individual.
28+
29+
* Inclusivity: We innovate through different perspectives and skill sets, which
30+
can only be accomplished in a welcoming and respectful environment.
31+
32+
* Participation: Responsibilities within the project are earned through
33+
participation, and there is a clear path up the contributor ladder into leadership
34+
positions.
35+
36+
## Maintainers
37+
38+
SOPS Maintainers have write access to the [getsops GitHub Organization](https://github.com/getsops).
39+
They can merge their own patches or patches from others. The current maintainers
40+
can be found in [MAINTAINERS.md](./MAINTAINERS.md). Maintainers collectively manage the project's
41+
resources and contributors.
42+
43+
This privilege is granted with some expectation of responsibility: maintainers
44+
are people who care about the SOPS project and want to help it grow and
45+
improve. A maintainer is not just someone who can make changes, but someone who
46+
has demonstrated their ability to collaborate with the team, get the most
47+
knowledgeable people to review code and docs, contribute high-quality code, and
48+
follow through to fix issues (in code or tests).
49+
50+
A maintainer is a contributor to the project's success and a citizen helping
51+
the project succeed.
52+
53+
The collective team of all Maintainers is known as the Maintainer Council, which
54+
is the governing body for the project.
55+
56+
### Becoming a Maintainer
57+
58+
To become a Maintainer you need to demonstrate the following:
59+
60+
* commitment to the project:
61+
* participate in discussions, contributions, code and documentation reviews
62+
* perform reviews for non-trivial pull requests,
63+
* contribute non-trivial pull requests and have them merged,
64+
* ability to write quality code and/or documentation,
65+
* ability to collaborate with the team,
66+
* understanding of how the team works (policies, processes for testing and code review, etc),
67+
* understanding of the project's code base and coding and documentation style.
68+
69+
A new Maintainer must be proposed by submitting an [Issue to the community repository](https://github.com/getsops/community/issues). A simple majority vote of existing Maintainers
70+
approves the application. Maintainers nominations will be evaluated without prejudice to employer or demographics.
71+
72+
Maintainers who are selected will be granted the necessary GitHub rights,
73+
and invited to the private maintainer mailing list.
74+
75+
### Removing a Maintainer
76+
77+
Maintainers may resign at any time if they feel that they will not be able to
78+
continue fulfilling their project duties.
79+
80+
Maintainers may also be removed after being inactive, failure to fulfill their
81+
Maintainer responsibilities, violating the Code of Conduct, or other reasons.
82+
Inactivity is defined as a period of very low or no activity in the project
83+
for a year or more, with no definite schedule to return to full Maintainer
84+
activity.
85+
86+
A Maintainer may be removed at any time by a 2/3 vote of the remaining maintainers.
87+
88+
Depending on the reason for removal, a Maintainer may be converted to Emeritus
89+
status. Emeritus Maintainers will still be consulted on some project matters,
90+
and can be rapidly returned to Maintainer status if their availability changes.
91+
92+
## CNCF Resources
93+
94+
Any Maintainer may suggest a request for CNCF resources. A simple majority of Maintainers approves the request. The Maintainers
95+
may also choose to delegate working with the CNCF to non-Maintainer community
96+
members, who will then be added to the [CNCF's Maintainer List](https://github.com/cncf/foundation/blob/main/project-maintainers.csv)
97+
for that purpose.
98+
99+
## Code of Conduct
100+
101+
[Code of Conduct](./CODE_OF_CONDUCT.md)
102+
violations by community members will be discussed and resolved
103+
amongst maintainers. If a Maintainer is directly involved
104+
in the report, the Maintainers will instead designate two Maintainers to work with the CNCF Code of Conduct Committee in resolving it.
105+
106+
## Voting
107+
108+
While most business in SOPS project is conducted by "[lazy consensus](https://community.apache.org/committers/lazyConsensus.html)",
109+
periodically the Maintainers may need to vote on specific actions or changes.
110+
A vote can be taken for security or conduct matters. Any Maintainer may
111+
demand a vote be taken.
112+
113+
Most votes require a simple majority of all Maintainers to succeed, except where
114+
otherwise noted. Two-thirds majority votes mean at least two-thirds of all
115+
existing maintainers.
116+
117+
## Modifying this Charter
118+
119+
Changes to this Governance and its supporting documents may be approved by
120+
a 2/3 vote of the Maintainers.

‎README.md‎

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,7 @@
11
# SOPS Community
22

3-
> **Note**
4-
>
5-
> After being [accepted into the CNCF as a Sandbox project][sandbox-application],
6-
> we are bootstrapping our way into a proper GitHub organization. This
7-
> effectively means this repository is still in its infancy, while we work
8-
> through the [onboarding process][sandbox-onboarding].
3+
Resources for engagement with the [getsops](https://github.com/getsops) community.
94

10-
[sandbox-application]: https://github.com/cncf/sandbox/issues/28
11-
[sandbox-onboarding]: https://github.com/cncf/toc/issues/1057
5+
* [Code of Conduct](./CODE_OF_CONDUCT.md)
6+
* [Governance](./GOVERNANCE.md)
7+
* [Maintainers](./MAINTAINERS.md)

0 commit comments

Comments
 (0)