All: There have been discussions amongst e.g. Jason, Shaun, Michael, myself, Brian Proffitt, and maybe others around how we want to use and avoid misusing GitHub as part of our writing workflow. This topic is of general interest to other writers we know who work on upstream documentation in various ways. https://github.com/theopensourceway/guidebook My thinking/guidance is mainly: 1. Let's make sure we can get work done toward our goal -- writing, editing, publishing in a way that works for the contributors is top priority. 2. Don't paint ourselves into any corners, i.e. lock ourselves into a forever-stuck-on-GitHub tooling.\ In support of #2, I think it would be good to say that our decisions here are to cover the production of the 2.0 work. At that time we take a serious review of our experiences so far and see how we can move toward 100% FOSS for all parts of the project. For #1, what do you all think? How do you want to use PRs and Issues around writing chapters and sections? 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://theopensourceway.org gpg: AD0E0C41 | https://red.ht/sig