Require all k/* repositories to have CONTRIBUTING.md

[guineveresaenger]

All K8s subrepositories should have a CONTRIBUTING.md file, which at the minimum should point to
https://github.com/kubernetes/community/blob/master/contributors/guide/README.md. Care should be taken that all information is in sync with the contributor guide.

Subrepositories may also have contributing guidelines specific to that repository. They should be explicitly documented and explained in the CONTRIBUTING.md.

The first step to working on this issue is to create a task list of k/subrepositories that need to have issues/PRs filed against to rectify this.

/sig contributor-experience
/area contributor-guide
/help

[k8s-ci-robot]

@guineveresaenger:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

All K8s subrepositories should have a CONTRIBUTING.md file, which at the minimum should point to
https://github.com/kubernetes/community/blob/master/contributors/guide/README.md. Care should be taken that all information is in sync with the contributor guide.

Subrepositories may also have contributing guidelines specific to that repository. They should be explicitly documented and explained in the CONTRIBUTING.md.

The first step to working on this issue is to create a task list of k/subrepositories that need to have issues/PRs filed against to rectify this.

/sig contributor-experience
/area contributor-guide
/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[chris-short]

Here are the following k/subrepositories with no CONTRIBUTING.md in their root dirs:

autoscaler
cloud-provider-aws
cloud-provider-azure
cloud-provider-gcp
cloud-provider-openstack
common
dashboard
examples
features
federation
gengo
kube-openapi
kube-state-metrics
kubernetes-anywhere
kubernetes-bootcamp
node-problem-detector
publishing-bot
repo-infra
sig-release
utils

[nikhita]

@guineveresaenger Could this be a good first issue as well? :)

The approach I see here is:

1. Go to each repo (from @chris-short's list above) and create an issue about adding a CONTRIBUTING.md to their repo. Mention that they can point to https://github.com/kubernetes/community/blob/master/contributors/guide/README.md if they don't want to include any specific contributing guidelines.
2. If the maintainers of the repo decide not to create specific contributing guidelines, perhaps even send a PR creating a CONTRIBUTING.md which has a link to https://github.com/kubernetes/community/blob/master/contributors/guide/README.md.

[guineveresaenger]

I think this is an excellent first issue!
/good-first-issue

[k8s-ci-robot]

@guineveresaenger:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

I think this is an excellent first issue!
/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[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

[nikhita]

This issue is being tracked in steering (kubernetes/steering#28) and has more discussion there. I'll close this issue here. Please reopen if needed.

/close

[k8s-ci-robot]

@nikhita: Closing this issue.

In response to this:

This issue is being tracked in steering (kubernetes/steering#28) and has more discussion there. I'll close this issue here. Please reopen if needed.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.