Would a best practice guide be helpful?

[Trilarion]

I thought about it for a while and I wonder if a hand book / guide about best practices for open source projects would be a helpful idea? What it would probably include, would be topics like:

• Choice of the name (avoid prefixes like Open / Free / SDL)
• Source versioning
• License information (where to display, what is popular, include artwork licenses)
• Dependencies (which ones are popular, where to find information about them)
• Build systems (the choices, where to find information about them)
• Distribution of binaries
• Continuous integration
• Bug reports
• …

Or is this already existing? It could be geared toward games development though maybe.

[Trilarion]

Might be interesting: Free and open source development practices in the game community but unfortunately behind paywall. Search directly on the authors homepage or get the text by other means and then summarize here. Is from 2004, so may also be outdated. However, may be a good start for a literature search.

[Trilarion]

Also see https://modelviewculture.com/resources#engineering for pitfalls like toxic cultures.