Skip to content

Commit a9c0462

Browse files
committed
Add GitHub Admin Team to governance
Signed-off-by: Marvin Beckers <[email protected]>
1 parent b93ff63 commit a9c0462

File tree

2 files changed

+27
-12
lines changed

2 files changed

+27
-12
lines changed

GOVERNANCE.md

Lines changed: 21 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,27 @@ the project succeed.
6464
The collective team of all Maintainers is known as the Maintainer Council, which
6565
is the governing body for the project.
6666

67+
### Security Response Team
68+
69+
The Maintainers will appoint a Security Response Team to handle security reports.
70+
This committee may simply consist of the Maintainer Council themselves. If this
71+
responsibility is delegated, the Maintainers will appoint a team of at least two
72+
contributors to handle it. The Maintainers will review who is assigned to this
73+
at least once a year.
74+
75+
The Security Response Team is responsible for handling all reports of security
76+
holes and breaches according to the [security policy](./SECURITY.md).
77+
78+
The members of the Security Response Team are documented in [MAINTAINERS.md](./MAINTAINERS.md).
79+
80+
### GitHub Admin Team
81+
82+
The maintainers will appoint a GitHub Admin Team to handle ownership of the GitHub organization(s) owned by the kcp project. Members of the GitHub Admin Team need to be extremely trustworthy individuals with a long-standing trusted relationship to the project.
83+
84+
The team's responsibility is being administrators for the GitHub organization(s). This would include managing organization-wide permissions, creating new repositories, configuring the organization, etc. The GitHub Admin Team is an executive organ of the full Maintainer Council with the goal to reduce broad permissions, but members of the team are bound by Maintainer Council decisions. Members of the GitHub Admin Team must not be from a single employer/organization.
85+
86+
The members of the GitHub Admin Team are documented in [MAINTAINERS.md](./MAINTAINERS.md).
87+
6788
## Becoming a Maintainer
6889

6990
<!-- If you have full Contributor Ladder documentation that covers becoming
@@ -133,18 +154,6 @@ Code of Conduct violations happen through the [CNCF Code of Conduct committee](.
133154
and kcp maintainers pledge to work with the committee to resolve any incidents
134155
occurring in the kcp community.
135156

136-
## Security Response Team
137-
138-
The Maintainers will appoint a Security Response Team to handle security reports.
139-
This committee may simply consist of the Maintainer Council themselves. If this
140-
responsibility is delegated, the Maintainers will appoint a team of at least two
141-
contributors to handle it. The Maintainers will review who is assigned to this
142-
at least once a year.
143-
144-
The Security Response Team is responsible for handling all reports of security
145-
holes and breaches according to the [security policy](./SECURITY.md).
146-
147-
The members of the Security Response Team are documented in [MAINTAINERS.md](./MAINTAINERS.md).
148157

149158
## Voting
150159

MAINTAINERS.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,3 +23,9 @@ The following maintainers are members of the security response team and enact th
2323
- Dr. Stefan Schimanski
2424
- Mangirdas Judeikis
2525
- Marvin Beckers
26+
27+
## GitHub Admin Team
28+
29+
The following maintainers are members of the GitHub Admin Team and manage the GitHub organizations:
30+
31+
- TBD

0 commit comments

Comments
 (0)