You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: GOVERNANCE.md
+21-12Lines changed: 21 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,6 +64,27 @@ the project succeed.
64
64
The collective team of all Maintainers is known as the Maintainer Council, which
65
65
is the governing body for the project.
66
66
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
+
67
88
## Becoming a Maintainer
68
89
69
90
<!-- 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](.
133
154
and kcp maintainers pledge to work with the committee to resolve any incidents
134
155
occurring in the kcp community.
135
156
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).
0 commit comments