Document recommended repo setup about kubernetes-template-project HOT 10 CLOSED

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.

from kubernetes-template-project.

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

from kubernetes-template-project.

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

from kubernetes-template-project.

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

from kubernetes-template-project.

/remove-lifecycle rotten

from kubernetes-template-project.

@spiffxp is working on related issues

from kubernetes-template-project.

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

from kubernetes-template-project.

/remove-lifecycle stale

from kubernetes-template-project.

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

from kubernetes-template-project.

/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

from kubernetes-template-project.