[Contrib] Splitting up the repo to specific & general

In the meeting today I brought up the question of if we are jamming too many meta activities into the repo that should be focused on being source for the guidebook. Currently we have guide-specific project boards mixed with project-wide boards. The proposal here is to separate the specific from the general. The general needs a new repo name, so get out your favorite bikeshed colors. Talking it through with Ashley, and following our own practice of not over-complicating when simple will do, it made sense to have just one new "meta" repo that contains project wide content, tools, etc. We would want to finish renaming the primary branch to 'main' before doing this split, moving issues to the new repo, etc. How does this look? current ======= github/theopensourceway/guidebook.git |_ marketing/ |_ mediawiki-source-content |_ templates/ Project boards for guidebook.git 1. Editorial (guide content only) 2. Governance (project governance) 3. Marketing (guide and project marketing) 4. Technical (project tooling, incl guide build tools) proposed ======== github/theopensourceway/guidebook.git |_ mediawiki-source-content |_ templates/ github/theopensourceway/project-all.git <== BIKESHED ME PLEASE |_ marketing/ |_ marketing/blog-posts |_ tools/ |_ ... Project boards for guidebook.git 1. Editorial (guide content only) Project boards for project-all.git 1. Governance (project governance) 2. Marketing (guide and project marketing) 3. Technical (project tooling, incl guide build tools) Best, - Karsten -- Karsten Wade [he/him/his]| Senior Community Architect | @quaid Red Hat Open Source Program Office (OSPO) : @redhatopen https://community.redhat.com | https://next.redhat.com | https://osci.io https://theopensourceway.org | https://github.com/theopensourceway/guide