I haven't read through all the guides -- they are very helpful

• Different formats for the guide -- there is so much content to read, I would like to read it in PDF form or on a kindle. (Dare I say - audio? I learn better that way.
• Governance models
  • models of governance & examples
  • what hierarchy and when in the lifecycle
  • what is too much structure too early and what is not enough
• CoC suggested procedures - and how to do the hard stuff
  • Example of how to make difficult decisions and use enforcement
• How to offboard someone from your project (eg revoking accesses)
• How / when to archive a project

• Handling growth of a project and what you should do at each stage

Happy to help on it if interested.

One idea: A guide on securing your project’s dependencies. Many open source maintainers rely on npm packages or other ecosystems, but don’t have good visibility into supply chain risks. A guide could cover things like detecting malicious packages, vetting new dependencies, using tools like Socket, and reducing attack surface. Would be super helpful for both new and experienced maintainers. Happy to help outline this if useful.