summaryrefslogtreecommitdiff
path: root/github-management
diff options
context:
space:
mode:
authorChristoph Blecker <admin@toph.ca>2018-08-07 12:44:17 -0700
committerChristoph Blecker <admin@toph.ca>2018-08-07 12:44:17 -0700
commit22f00f26090af5f257b4959a5e069aec598c5137 (patch)
tree0f9de71ed831269ce92eef54ddb3569f6114fadc /github-management
parentfd85fc9afccbfe68faa3455c6fe39cf2c4532a0b (diff)
Add information on GAT SLOs
Diffstat (limited to 'github-management')
-rw-r--r--github-management/org-owners-guide.md24
1 files changed, 24 insertions, 0 deletions
diff --git a/github-management/org-owners-guide.md b/github-management/org-owners-guide.md
index ad7c8a7e..0ac510d9 100644
--- a/github-management/org-owners-guide.md
+++ b/github-management/org-owners-guide.md
@@ -4,6 +4,26 @@ The Kubernetes project leverages multiple GitHub organizations to store and
organize code. This guide contains the details on how to run those organizations
for CNCF compliance and for the guidelines of the community.
+## SLOs
+
+The [GitHub Administration Team] will aim to handle requests in the following
+time frames:
+- Organization invites should be handled within 72 hours of all requirements for
+ membership being met (all +1s obtained).
+- Repository creation or migration requests should be responded to within 72
+ hours of the issue being opened. There may be information required or specific
+ requirements that take additional time, but once all requirements are met, the
+ repo should be created within 72 hours.
+- Security or moderation requests should be handled ASAP, and coverage should be
+ provided in multiple time zones and countries.
+- All other requests should be responded to within 72 hours of the issue being
+ opened. The time to resolve these requests will vary depending on the
+ specifics of the request.
+
+If a request is taking longer than the above time frames, or there is a need to
+escalate an urgent request, please mention **[@kubernetes/owners]** on the
+associated issue for assistance.
+
## Organization Naming
Kubernetes managed organizations should be in the form of `kubernetes-[thing]`.
@@ -60,3 +80,7 @@ for all orgs going forward. Notable discrepancies at the moment:
Repositories have additional guidelines and requirements, such as the use of
CLA checking on all contributions. For more details on those please see the
[Kubernetes Template Project](https://github.com/kubernetes/kubernetes-template-project), and the [Repository Guidelines](kubernetes-repositories.md)
+
+
+[GitHub Administration Team]: /github-management/README.md#github-administration-team
+[@kubernetes/owners]: https://github.com/orgs/kubernetes/teams/owners