Merge pull request #2493 from cblecker/org-slo

Add information on SLOs and how to open a request

github-management/README.md

@@ -14,6 +14,7 @@ These polices are overseen by the
 Experience Special Interest Group.
 
 ## Guides
+- [Opening a request for assistance with GitHub](opening-a-request.md)
 - [Organization Owners Guide](org-owners-guide.md)
 - [Repository Creation Guidelines](kubernetes-repositories.md)
 - [Setting up the CNCF CLA Check](setting-up-cla-check.md)

github-management/opening-a-request.md

@@ -0,0 +1,33 @@
+# Opening a issue for support with GitHub
+
+## GitHub issues
+
+If you need help with the following:
+- Permissions issues
+- Organization membership
+- Third-party integrations
+- Webhooks
+- Repository creation/migration
+- Repository archival
+- Other repository and configuration issues
+
+Please open an issue against the [kubernetes/org] repository describing your
+issue. If your request is urgent, please escalate to **[@kubernetes/owners]**.
+
+## Bot/Automation issues
+
+If you need help with the following:
+- Bot configuration
+- Automatic merging
+- Label issues
+- Automation feedback and feature requests
+
+Please open an issue against the [kubernetes/test-infra] repository describing
+your issue. If your request is urgent, please escalate to the
+[test-infra on-call] or reach out to `#testing-ops` on Slack.
+
+
+[kubernetes/org]: https://github.com/kubernetes/org/issues
+[@kubernetes/owners]: https://github.com/orgs/kubernetes/teams/owners
+[kubernetes/test-infra]: https://github.com/kubernetes/test-infra/issues
+[test-infra on-call]: https://go.k8s.io/oncall

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