Document WireMock project governance

[oleg-nenashev]

Proposal

At the moment there is no governance for the WireMock organization documented. Apart from the Code of Conduct requested in #4, we need to document how the decisions are made in the community, including technical and community decisions. Also, if there is interest to introduce any entities, it would be nice to do so. The same go to the component governance (e.g. Docker image or Python SDK) that might need a change

For the moment, I propose the following de-facto governance model:

• We intend to do key decision and discussions in the community channels (Slack, Mailing list), and want to build a consensus when possible
• @tomakehurst acts as a BDFL and a lead maintainer who has a final say on wiremock/wiremock development and general direction of the project
• All components within the WireMock GitHub organization have maintainers, who again have a final say for the changes within their components
• Components outside of the GitHub organization are solely governed by their owners/maintainers, and not considered a part of this governance

Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.

• Jenkins Governance: model https://www.jenkins.io/project/governance/
• Meritocracy 2.0: https://opensource.com/open-organization/16/6/presenting-framework-meritocracy

[oleg-nenashev]

I published the document as a preview. Feedback is welcome!

[oleg-nenashev]

Merged: https://github.com/wiremock/community/tree/main/governance