diff --git a/GOVERNANCE.md b/GOVERNANCE.md
new file mode 100644
index 00000000..5de6e8f2
--- /dev/null
+++ b/GOVERNANCE.md
@@ -0,0 +1,74 @@
+# AssaultCube Pragmatic Governance Model (ACPGM) 
+
+Status: Draft
+
+## Purpose
+
+AssaultCube is an open-source project maintained by various people around the globe. These people invest their free time and consider their involvement as a hobby. 
+Because people come and go, there is an inherent risk that ownership of the project will be lost and a power vacuum will bog the project down.
+
+ACPGM is a lightweight governance model that supports the continuity and longevity of the project. It is designed to support the people involved in moving the project forward. 
+It is simple enough to be practically useful and complex enough to prevent ambiguity. After all, it should be fun to engage in the project - nobody wants bureaucracy.
+ACPGM is not legally binding and does not constitute a legal entity.
+
+## Community
+
+- The number of community members must be at lest twenty. The community decides with relative majority vote.
+- Rights
+  - The community own AssaultCube. 
+  - The community elect the members of the committee. This election is held once a year in February in the AC forum.
+  - If the committee excludes a community member, the community members can reject this decision.
+  - The community decides on proposed changes to this governance model.
+- Community members shall donate USD $25 per year through the existing donation mechanism to pay the bills for hosting (includes masterserver, forum, website, wiki). Surplus amounts can be used for AC tournaments.
+- Applications for joining shall be addressed to the committee which shall decide upon acceptance or non-acceptance.
+
+## Committee
+
+- The number of committee members must be at least three. The committee decides with relative majority vote.
+- The goal of the committee is to
+  -  Ensure the longevity of the project
+  -  Balance tradition with innovation
+  -  Promotion of youg talents
+- Rights
+  - The committee may invite or exclude community members any time.
+  - The committee may invite or exclude platform team members any time.
+  - The committee may invite or exclude dev team members any time.
+  - The committee dedices which of the committee member has the role of the _Chairman_. The Chairman represents the committee towards others to simplify communication.
+  - The committee has full authority of the project if not stated otherwise in this governance model.
+
+## Platform Team
+
+- The number of platform team members is at least three. The platform team is self-oranizing.
+- The goal of the platform team is to
+  - Keep up the game infrastructure and protect the game from attacks and abuse
+  - Provide the service of fair and transparent moderation and game jurisidication (e.g. bans)
+  - Establish welcoming culture and support civil/non-violent discussions
+- Rights
+  - The platform team operates the infrastructure of AssaultCube and governs all administrative rights/permissions.
+  - The platform team represents the highest decision authority in terms of community moderation and game jurisdication.
+  - The platform team dedices which of the platform team member has the role of the team lead. The team lead represents the platform team towards others to simplify communication.
+- The platform team publishes its own policies regarding community moderation and game jurisication.
+
+## Dev Team
+
+- The number of dev team members is at least three. The dev team is self-organizing.
+- The goal of the dev team is to
+  - Conceptualize and execute a Strategy for AC [1]
+  - Publish an AC release at least once a year [2]
+  - Actively acquire new talents for the project and provide mentorship
+- Rights
+  - The dev team dedices on development priorites, inclusion of features and bugfixes
+  - The dev team may change minor gameplay-relevant aspects of the game, major aspects require approval by the committee [3]
+  - The dev team dedices which of the dev team member has the role of the team lead. The team lead represents the dev team towards others to simplify communication.
+
+## More
+
+- Experience shows that people find it difficult to have multiple roles (different "hats") and to apply the right role depending on the context. Therefore, a person can *formally* belong to only one of these three groups: committee, dev team, platform team. In practice however, people can support the project in different areas.
+
+## Remarks
+
+[1] The people that want to put their time into improving and advancing AC to the next level should be provided a lot of freedom. This makes the project attractive for talents. The people that have the ideas should be the same people that build the stuff. Therefore it is better to give the dev team authority over vision/strategy instead of giving this authrity to the committee. The committee can still influence the broad direction of the project by setting up the dev team accordingly.
+
+[2] This ensure the knowledge of publishing a release remains active. A release could potentially only contain new maps/media worst-case.
+
+[3] Example: Minor gameplay change would be making the physics of nades more realistic; major gameplay change would be tweaking gun damage.