My personal number one measure of module quality is documentation, hands down.
Nothing else comes close.
That means a README that provides a good overview of the module’s structure,
scope, requirements, and capabilities, and a *thorough* REFERENCE(.md)
document. As a module quality considerat
Posting manually since Google Groups doesn't seem to like my ProtonMail
E-Mail:
I think we are looking at a couple different discussions here:
- Module Quality
- Code Quality
I think the former is always going to be difficult to track in any
meaningful way, largely because expectation
I've certainly got a few opinions.
I think that the following are mandatory:
- rspec-puppet tests (that pass)
- beaker, litmus, or test-kitchen tests (that pass)
- Critical path test coverage that matches your supported operating
systems (as much as is reasonable)
- Documented para
