[docs] Add Governance overview and Teams structure

Signed-off-by: Konstantin Pastbin <konstantin.pastbin@gmail.com>

docs/GOVERNANCE.md

@@ -0,0 +1,20 @@
+# Governance
+
+The Organic Maps project is community-driven and has little hierarchy.
+
+## [The Board](GOVERNANCE/BOARD.md)
+Ensures the project stays within its [Mission and Core Values](CORE_VALUES.md),
+legally hosts project's assets like trademarks, domains, finances etc. and handles legal enquiries.
+See [details](GOVERNANCE/BOARD.md) of Board's structure and responsibilities.
+
+## [Teams](GOVERNANCE/TEAMS.md)
+
+Day-to-day work and decisions are made by the teams of active contributors ("the doers") in their area of expertise, e.g. Android development, translations or devops, see [the full list of Teams](GOVERNANCE/TEAMS.md).
+
+At the moment there is no formal process to resolve non-technical disputes (e.g. UX disagreements or whether a proposed change fits into OM at all),
+but there are some common sense guidelines / recommendations:
+  - strive to address all reasonable concerns
+  - ask more contributors and experts on the matter to provide their opinion
+  - refer to users' feedback, e.g. include the change into an alpha version or poll via communication channels
+  - usually an incremental improvement is better than no change at all, create separate issues for follow-up concerns
+  - give benefit of a doubt to the actual "doers" who commit their energy into code, designs, etc.

docs/GOVERNANCE/TEAMS.md

@@ -0,0 +1,47 @@
+# Teams
+
+A team is a group of people who work together on a specific area to further Organic Maps.
+Team pages list responsibilities, active contributors ("doers") and permissions they hold, as well as links to team-specific docs and resources.
+
+Its not necessary to be a part of a team in order to submit a PR, take part in a discussion or otherwise participate in team's work.
+People listed there are the most active contributors and "go to" persons, so that its clear whom to ask questions, request reviews, etc.
+They could be trusted with extra permissions and accesses necessary for their work (e.g. merge rights).
+
+If you've been contributing actively then feel free to open a PR/issue to add yourself to relevant teams and/or request permissions needed to facilitate your work.
+
+- RELEASE
+<br>stores accs, maps generation, alphas/betas
+
+- COMMS
+<br>announcements (chats, social media, web site news), moderation
+
+- USER SUPPORT
+<br>feedback in stores, emails, social media, managing issues, user-facing docs (FAQs)
+
+- TRANSLATIONS
+<br>UI strings, store descriptions, rel notes, etc.
+
+- DESIGN
+<br>UI, UX, graphic design, product design
+
+- GROWTH and SUSTAINABILITY
+<br>marketing (SEO/ASO/SMM), user research, fundraising (donations, grants, monetization), attraction, retention and funding of contributors, financial transparency
+
+- EXPERTS
+<br>subject matter experts and talent in different fields, willing to share their knowledge
+
+- ANDROID
+
+- IOS
+
+- MAPS
+<br>map data, styles
+
+- APP CORE
+<br>rendering, routing, search, editor, bookmarks & tracks, maps generator, desktop and mobile linux versions, etc.
+
+- DEVOPS
+<br>servers / cdn, CI/CD, tooling
+
+- ADMINS
+<br>manage individual and team permissions