Merge pull request #3 from cblecker/issue-template

Add issue templates

.github/ISSUE_TEMPLATE/general-support.md

@@ -0,0 +1,14 @@
+---
+name: General Support
+about: Permissions issues, repository issues, etc
+
+---
+
+### Organization or repository
+e.g. kubernetes/kubernetes
+
+### Users effected
+e.g. (at)example_user
+
+### Describe the issue
+A clear and concise description of what you need assistance with.

.github/ISSUE_TEMPLATE/integrations.md

@@ -0,0 +1,20 @@
+---
+name: Integrations
+about: Third-party integrations, webhooks, or GitHub Apps
+
+---
+
+### Organization or repository
+e.g. kubernetes/kubernetes
+
+### Name of integration
+e.g. travis
+
+### Link to integration website
+e.g. https://travis-ci.org/
+
+### Describe what is attempting to be accomplished
+A clear and concise description of what is trying to be accomplished with this integration.
+
+### Additional context for request
+Any additional information or context to describe the use case.

.github/ISSUE_TEMPLATE/membership.md

@@ -0,0 +1,31 @@
+---
+name: Organization Membership Request
+about: Request membership in a Kubernetes Org
+
+---
+
+### GitHub Username
+e.g. (at)example_user
+
+### Organization you are requesting membership in
+e.g. (at)kubernetes
+
+### Requirements
+- [ ] I have reviewed the community membership guidelines (https://git.k8s.io/community/community-membership.md)
+- [ ] I have enabled 2FA on my GitHub account (https://github.com/settings/security)
+- [ ] I have subscribed to the kubernetes-dev e-mail list (https://groups.google.com/forum/#!forum/kubernetes-dev)
+- [ ] I am actively contributing to 1 or more Kubernetes subprojects
+- [ ] I have two sponsors that meet the sponsor requirements listed in the community membership guidelines
+- [ ] I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application
+
+### Sponsors
+- (at)sponsor-1
+- (at)sponsor-2
+
+### List of contributions to the Kubernetes project
+- <PR reviewed / authored>
+- <PR reviewed / authored>
+- <Issue responded to>
+- <Issue responded to>
+- <SIG project I am involved with>
+- <SIG project I am involved with>

.github/ISSUE_TEMPLATE/repo-archive.md

@@ -0,0 +1,17 @@
+---
+name: Repository archival
+about: Retire and archive a Kubernetes repository
+
+---
+
+### Repository to archive
+e.g. kubernetes/old-project
+
+### Repository and/or sig subproject owners that are approving this archival
+e.g. (at)example_user
+
+### When should this be done
+e.g. Anytime.
+
+### Additional context for request
+Any additional information or context to describe the request.

.github/ISSUE_TEMPLATE/repo-create.md

@@ -0,0 +1,27 @@
+---
+name: Repository creation/migration
+about: Create or migrate a repository into a Kubernetes Org
+
+---
+
+### New Repo, or migrate existing
+e.g. new repository
+
+### Requested name for new repository
+e.g. cloud-provider-foo
+
+### Which Organization should it reside
+e.g. kubernetes-sigs
+
+### Who should be provided access to this repository
+e.g (at)example_user should have write access
+
+### Approvals
+Please detail out the approval process for the new repo
+Requirements are listed here: https://git.k8s.io/community/github-management/kubernetes-repositories.md
+If this is a core repository, then sig-architecture must approve
+If this is a SIG repository, then the SIG Technical Leads must approve
+Please include links to the approvals (meeting minutes, e-mail thread, etc)
+
+### Additional context for request
+Any additional information or context to describe the request.