[idea] Create cncf/community repo

[justaugustus]

In the Kubernetes project, we have the https://github.com/kubernetes/community, which serves as one of the primary ingresses points for contributors.

It would be cool to have something analogous within the CNCF GitHub org.
I currently see https://github.com/cncf/contribute, which is close and could potentially be renamed/used for this purpose.

cc: @parispittman @jberkus @gerred @amye @idvoretskyi
ref: #3

[idvoretskyi]

@justaugustus the purpose of creating of the c/contribute repo was about the same, let's use it, happy to help with this.

Also, I'd prefer not to rename it unless strongly necessary.

[justaugustus]

Okay, cool! I'll raise this on Thursday's SIG call.

[idvoretskyi]

@justaugustus np, thanks!

[parispittman]

this is mostly done based on our convo at the meeting re: why and what repos we have like cncf/contribute and cnc/sig-contrib...i think to close this issue we should do the following:

• add a description of the repos we have on our CONTRIBUTING.md [x] and README.md [open]

• think about / discuss (not necessarily take action) on the concept of mapping the repos/lower level directories to our working groups on the README (this could also go under the gh ContribStrat GitHub Management #5 issue, too maybe)

wdyt?

[carolynvs]

I wanted to bring some discussions that happened on Slack and in documents elsewhere back here. We have been talking about breaking out our content like so:

• cncf/sig-contributor-strategy - internal docs for the sig.
• cncf/contribute - external docs such as a contributing.md template or "how to create a contributor ladder” guide and best practices published by this group.

After bringing up the templates to a wider audience, people said that cncf/contribute was already established for new contributors to the CNCF and that these templates didn't fit into that purpose. cncf/contribute#36

Maybe I completely misunderstood the plans for cncf/contribute, and if so I'm sorry for the confusion. Please jump in and correct me if that's the case. I just wanted to lay out the types of content we have and potential homes for it:

• internal sig docs - same in this repo
• templates - new repo (maybe cncf/project-template?) that we can make a github template repository so that a project could create a new repo from our templates using a big green button.
• external docs - new repo (maybe cncf/community as originally proposed?) that we could eventually turn into a website not just github readmes gallore.

[parispittman]

https://github.com/cncf/project-template has been created. Closing this issue has I believe it meets Carolyn and Stephen's ideas and needs.

/close