General laundry list of things that I see CNCF wants (from their charter + project template & its github pages docs) filtered through some of my own thoughts and others (like from opensource.guide).

Still reading a bit on the implications on donating the project (had a break from thinking about this), but i think many things that are asked for are from CNCF are good things to have in a project anyway so listing out a few of them as I come across them.

NB: Closed the previous issue in #586 that was specific to donating to kubernetes or kubernetes-client org (i.e. no longer talking about merge/triage bots, stale-closers, or copyright headers), and I no longer think this is right for us.

• roadmap - Kube Roadmap (view) + pinned umbrella issues
• maintainers file (optional) - done in Maintainers + Governance + Security docs #671
• governance documents (not needed for sandbox afaikt - and once again linkerd has an easier alternative template) - done in Maintainers + Governance + Security docs #671
• security.md (simple linkerd variant) - done in Maintainers + Governance + Security docs #671
• guidelines for project contributors + code of conduct - done in cncf code of conduct #593
• issue templates and better contributing guidelines - add issue template + improve contributor help docs #699
• justifications for being donated and how we fit into the ecosystem (decent ones via donation of kube-rs to cncf #584)
• artwork finalization Refine our logo #570 - leaving this in the original issue - not necessary to do here, but would be nice.

Some other potential points (might re-raise these later to avoid this issue growing too much)

• ensure contributors are recognised better (mentioned in release info - communication)
• maybe invite people to help triage issues as a starting step to help contributing

Good background talks here:

• Turn Contributors into Maintainers with TAG Contributor Strategy.
• From Storming to Performing: Growing Your Project's Contributor Experience