Additionally we talked about a set of rules that should apply to Flowpack packages and in extension also to Neos packages which are handled even “stricter” obviously.
This are the first rough ideas:
Possible Flowpack Rules
MUST
Follow Neos coding guidelines
Should provide versions working with all maintained Flow/Neos versions (within time X after release)
have tests and test automation
package is considered stable and has been in use before moving to Flowpack
SHOULD
at least one team member constributes
Security maintenance
Contact person/group defined
At least very solid readme to describe installation and getting it running as well as options
great initiative, thanks for working on this topic!
As already mentioned before, I would like to see general guidelines about the repository names as well. We currently mix <composer-name-without-vendor> and <Package.Key> .
Obviously there are more important things, especially when you work exclusively with composer. But as you’re on it…
@samuel.hauser continue to work on it today by adding basic content page support and showcase the list of Flowpackers and contributors list for each package.