We are in the process of creating best-practice standards for the Blockchain Commons release path. We use as our inspiration, the Core Infrastructure Best Practices badge and other similar systems. What follows if our first-cut look at what standards we would like products to meet as they advance along the release path. We omit some from sources like Core Infrastructure (such as the need for a stable website and the ability to report bugs) because we believe the requirements our implicit in our use of GitHub.
- none currently
- Have working build
- Include Full attribution
- Post Open license
- Write Basic installation & usage instructions
- Acknowledge issues & PRs
- Add static analysis tools to test suite
- Complete Website (or GitHub) so it says what the product does and where to get it
- Community members assess usability
- Community members assess API
- Community members define additional requirements
- Community members report bugs or problems
- Community members provide docs for testing suites
- Complete security reviews
- Begin versioning releases
- Fix vulnerabilities within 60 days
At this time, this listing is very incomplete; additions and comments are very welcome. Ultimately, we would like any "Final:" program to approach or entirely meet standards like those in the Core Infrastructure best Practices.