Document recommended repo setup

[bgrant0607]

Forked from kubernetes/kops#644

I think it would be useful to describe the recommended setup for repos in the template.

For example, admin and maintainers (write) teams.

And how to turn on the bot. And copy labels.

And OWNERS.

Etc

cc @grodrigues3

[bgrant0607]

In the kubernetes-incubator org, ACL teams are named admins-repo and maintainers-repo. I prefer repo-admins (admin), repo-maintainers (write), and repo-collaborators (read). The teams are sorted alphabetically on the github UI, so putting the repo first groups them together. It's also handier for auto-completion.

[philips]

@sarahnovotny I think I wrote something somewhere at sometime. Do you remember where we put that?

[fejta-bot]

Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

[bgrant0607]

/remove-lifecycle rotten

[bgrant0607]

@spiffxp is working on related issues

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[cblecker]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[spiffxp]

/close
This is halfway done by docs in https://github.com/kubernetes/community/tree/master/github-management and I'd rather keep issues related to editing that over there