A few thoughts on sustain.md, posing the question: does it make sense to create a separate file?
First, @jdorfman kicked off development on it here: https://github.com/sustainers/sustain.md/pull/6
Information we started with:
- Who is maintainer and what is the bus factor.
- Where is funding coming from and how can one donate.
Second, what other information should a project provide in sustain.md to convince anyone that it is sustainable. (maybe not all of it belongs in the sustain.md but rather a badge)? Every idea that I come up with, I dismiss because there is a different place for this information. E.g. Code of Conduct best lives in its separate CODE_OF_CONDUCT.md file; What issue tracker to use lives in CONTRIBUTING.md; how to report software vulnerabilities lives in SECURITY.txt. …
Bringing these two thoughts together: Does it make sense to introduce yet another file or should we promote inclusion of our desired information within existing files?
Who the maintainers are would well fit within the README or CONTRIBUTING, same with how to contribute financially.