Improving on PR review process

[romaninsh]

Feature Request

Description

If Fomantic is to dash ahead with accepting some new features the one possible downfall would be the stability and introduced inconsistency. I propose that several "acceptance criteria" are introduced for new features and are maintained by contributors at all times:

• A process for reviewing new PRs to be documented
• Reviewer (who is not author of PR) is selected who is familiar with the process
• PR can only be accepted if Reviewer have approved it

Example Review criteria:

• Minor features must amend the documentation where required
• Major new modules must add a new documentation page
• New usage cases should be included on the UI testing page
• Test suite should snapshot new features or modifications
• New modules must have at least one test-case added to the "what's new" page.
• Major feature change can only have a mention on the release
• Any changes imported from SUI must reference original release note/PR
• Code/Docs/Examples must be stylistically consistent with the rest
• Modules with incomplete/unfinished API should be marked as "beta"

This is just an example, feel free to tweak. Following a criteria and keeping new feature quality in-check as well avoiding breaking changes is very important.