-
Notifications
You must be signed in to change notification settings - Fork 5.4k
Require all k/* repositories to have CONTRIBUTING.md #1832
Copy link
Copy link
Closed
Labels
area/contributor-guideIssues or PRs related to the contributor guideIssues or PRs related to the contributor guidegood first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.sig/contributor-experienceCategorizes an issue or PR as relevant to SIG Contributor Experience.Categorizes an issue or PR as relevant to SIG Contributor Experience.
Metadata
Metadata
Assignees
Labels
area/contributor-guideIssues or PRs related to the contributor guideIssues or PRs related to the contributor guidegood first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.sig/contributor-experienceCategorizes an issue or PR as relevant to SIG Contributor Experience.Categorizes an issue or PR as relevant to SIG Contributor Experience.
Type
Fields
Give feedbackNo fields configured for issues without a type.
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