Ensure all kubernetes repos follow the same contributing structure

[caniszczyk]

Some CNCF members have higher maintenance legal departments and require a bit more documentation in repos regarding contributing criteria. For example, there is the Kubernetes Contributor Guide that mandates that the CNCF CLA be signed and seems to apply to all code, but has a big disclaimer at the top which makes some legal departments wary. Some of the repo’s have a CONTRIBUTING.md file with a clear process which is good, others point to the Contributor Guide which is okay but many others have no such file – for example:

https://github.com/kubernetes/apiserver
https://github.com/kubernetes/cloud-provider-aws
https://github.com/kubernetes/cloud-provider-gcp
https://github.com/kubernetes/cloud-provider-openstack
https://github.com/kubernetes/common
https://github.com/kubernetes/dashboard
https://github.com/kubernetes/examples
https://github.com/kubernetes/federation
https://github.com/kubernetes/gengo
https://github.com/kubernetes/kube-openapi
https://github.com/kubernetes/kube-state-metrics
https://github.com/kubernetes/kubernetes-anywhere
https://github.com/kubernetes/kubernetes-bootcamp
https://github.com/kubernetes/node-problem-detector
https://github.com/kubernetes/publishing-bot
https://github.com/kubernetes/release
https://github.com/kubernetes/repo-infra
https://github.com/kubernetes/test-infra
https://github.com/kubernetes/utils

Can we ensure that every proper Kubernetes project has a CONTRIBUTING.md with terms clearly spelled out?

[cblecker]

@kubernetes/sig-contributor-experience-proposals @kubernetes/steering-committee

[philips]

I don't see any reason to not just ensure CONTRIBUTING.md is copied from https://github.com/kubernetes/kubernetes-template-project

Any opposition? If not I will file the issues across the repos.

Hey @jessfraz can you recommend a tool for filing issues like you did with #30

[cblecker]

cc @spiffxp who has also done many-repo issue/PR creation

[jessfraz]

It's just part of the tool I made for it. Opens an issue if an issue doesn't already exist and the file doesn't exist... https://github.com/jessfraz/secping Super hacky buyer beware.

[philips]

@jessfraz Great! I think I am going to just write a tool to ensure everyone's projects match the template project based on your code. :)

[philips]

For example, there is the Kubernetes Contributor Guide that mandates that the CNCF CLA be signed and seems to apply to all code, but has a big disclaimer at the top which makes some legal departments wary.

@caniszczyk Where is the above happening? I don't know exactly what you are talking about.

[philips]

I think largely this is an issue that @kubernetes/sig-contributor-experience-feature-requests needs to handle. Posted it over on their mailing list https://groups.google.com/forum/#!topic/kubernetes-sig-contribex/KqEXr5bVGDk

Happy to help though!

[jessfraz]

I can make the tool, would be super fast since it can use the same code :)

…

On Thu, Jul 5, 2018 at 9:31 PM Brandon Philips ***@***.***> wrote: I think largely this is an issue that @kubernetes/sig-contributor-experience-feature-requests <https://github.com/orgs/kubernetes/teams/sig-contributor-experience-feature-requests> needs to handle. Posted it over on their mailing list https://groups.google.com/forum/#!topic/kubernetes-sig-contribex/KqEXr5bVGDk Happy to help though! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#28 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABYNbDuTVUZ6RoDMq5xSvNv5HAsKeMPWks5uDr3igaJpZM4Ta-I2> .

-- Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 pgp.mit.edu <http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3>

[philips]

If you have time go for it! The only real change from the secping will be some of the files need to be more or less exact (LICENSE?) And in others just in the right format (OWNERs)

…

On Fri, Jul 6, 2018, 7:33 AM Jess Frazelle ***@***.***> wrote: I can make the tool, would be super fast since it can use the same code :) On Thu, Jul 5, 2018 at 9:31 PM Brandon Philips ***@***.***> wrote: > I think largely this is an issue that > @kubernetes/sig-contributor-experience-feature-requests > < https://github.com/orgs/kubernetes/teams/sig-contributor-experience-feature-requests > > needs to handle. Posted it over on their mailing list > https://groups.google.com/forum/#!topic/kubernetes-sig-contribex/KqEXr5bVGDk > > Happy to help though! > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#28 (comment) >, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/ABYNbDuTVUZ6RoDMq5xSvNv5HAsKeMPWks5uDr3igaJpZM4Ta-I2 > > . > -- Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 pgp.mit.edu < http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3> — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#28 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACDCNRK8bxUg--Fitpah9-RL_nsOKjeks5uD3UPgaJpZM4Ta-I2> .