Move common documentation to its own repo

[baude]

We have discussed in the past that we should create a repo in podman-container-tools that would store all of the governance, cncf documentation, meeting minute notes, etc. Today I think a lot of it lives in the podman repo with everything pointing to it; the proposal for that would to move to a new repo and everyone would still point at it.

This would also be nice because governance documentation changes would be namespaced out from podman making them more obvious to core-maintainers.

[Honny1]

Sounds good to me.

[baude]

perhaps we can use this issue to cite everything that needs to move.

[Luap99]

+1 But we should be clear on what kind of docs should move.

I see several categories which we may want to move/consolidate:

• CNCF governance files, GOVERNANCE.md ADOPTERS.md, ROADMAP.md?
• general contribution guidelines, i.e. CONTRIBUTING.md, LLM_POLICY.md, REVIEWING.md, SECURITY.md. I think it would help if we de duplicate across our repos.
• design docs, contrib/design-docs/? Since they can also be written for buildah, skopeo or for cross repo work like my config stuff I think it could make sense to have it not in podman.
• CI infrastructure notes, though I guess we should just use the "automation" repo for that as it houses the build scripts and so on.

[baude]

agree on all points

[danishprakash]

SGTM

---

• re: CONTRIBUTING.md; I believe a per-repo CONTRIBUTING.md sounds useful as per convention, not to mention, at least podman's CONTRIBUTING.md has some podman-specific bits (building, testing, docs, etc). We could have a generic contributing guidelines doc for someone wanting to contribute to projects under PCT but the respective per-repo guides can have more practical and specific instructions. At least I found them quite usefuel when I was starting out.
• Big +1 to moving design-docs/proposals to another repo (not sure if it has to be docs). I quite like how k8s does this with KEPs though they have significantly higher number of proposals. But the again, considering how closely overlapping the various projects under PCT are, a single destination for design-docs/proposals sounds like a good idea to me.

[Luap99]

re: CONTRIBUTING.md; I believe a per-repo CONTRIBUTING.md sounds useful as per convention, not to mention, at least podman's CONTRIBUTING.md has some podman-specific bits (building, testing, docs, etc). We could have a generic contributing guidelines doc for someone wanting to contribute to projects under PCT but the respective per-repo guides can have more practical and specific instructions. At least I found them quite usefuel when I was starting out.

Yes of course per repo things should stay in the repo, I was mostly thinking about the more general
https://github.com/podman-container-tools/container-libs/blob/main/CONTRIBUTING.md
https://github.com/podman-container-tools/container-libs/blob/main/CONTRIBUTING_GO.md

[nimbinatus]

I recommend calling it community. It's a common pattern now in the CNCF world (example: https://github.com/buildpacks/community), and it's a great place to collect application materials for the next step when you're ready.

[danishprakash]

JFYI: podman-container-tools/community#1