[docs] Add EXPERTS umbrella team

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

docs/GOVERNANCE.md

@@ -1,36 +1,20 @@
 # Governance
 
-Organic Maps Project (organicmaps.app) is an open-source project.
+The Organic Maps project is community-driven and has little hierarchy.
 
-## The Governing Board
+## [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.
 
-The focus of the Governing Board is to assist and guide in the progress and development of Organic Maps, as well as to lead and promote Organic Maps.
+## [Teams](GOVERNANCE/TEAMS.md)
 
-The Governing Board is the governing body responsible for the overall oversight of the Organic Maps Project. The Board also has the responsibility to ensure the goals, brands, and marks of Organic Maps and community are protected. The Board serves as the final authority within the Organic Maps Project.
+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).
 
-## Governing Board Responsibilities
-
-- Guidance and leadership over the ultimate Project roadmap.
-- Community outreach.
-- Maintenance of health and viability of the community.
-- Maintenance of a healthy and proactive relationship with the Project users and consider those needs and uses in decisions.
-- Coordination of Project messaging.
-- Overall Project leadership as the final escalation point for decisions.
-- Trademark and brand oversight.
-- Appointment of Board Chair.
-- Appointment of new Board members.
-- Re-appointment of Board members after 12 month term of service.
-
-## Chair Responsibilities
-
-- Organize and run the Board meetings.
-- Be the coordinating and lead voice for the Project.
-- Coordinate the Board to set direction and articulation thereof.
-- Focus on helping the Board to reach consensus.
-- Guide the Board in transparency and practicing the open source way in leadership and decision making.
-
-## Current Sitting Board
-
-- [Alexander Borsuk](https://github.com/biodranik)
-- [Victor Govako](https://github.com/vng)
-- [Roman Tsisyk](https://github.com/rtsisyk)
+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/ANDROID_TEAM.md

@@ -0,0 +1,41 @@
+# Android team
+
+- Android app development
+- Feature implementation
+- Testing and debugging
+- Performance optimization
+- Code review
+
+Together with the [iOS team](IOS_TEAM.md) strive for feature parity and UI/UX consistency across platforms.
+
+For UI/UX help ask the [Design team](DESIGN_TEAM.md).
+
+### Active contributors and their permissions
+- @rtsysik (merger)
+- @vng (merger)
+- @biodranik (merger)
+- @pastk (merger)
+- @kirylkaveryn (merger)
+- @redauburn (repo write)
+- @kavikhalique
+- @dvdmrtnz
+- @andrewshkrob (repo write)
+- @strump (repo write)
+- @map-per
+
+Android Auto developers and testers: @organicmaps/android-auto.
+
+Ask for technical reviews from @organicmaps/android (also see CODEOWNERS).
+At least one technical approval is required for a merge.
+
+Quality assurance:
+PR authors are expected to test their changes extensively and reviewers to help with it.
+But we'd love to have some people commited to testing specifically! Add yourself here!
+
+You don't have to be listed above to submit a PR occasionally, take part in a discussion or do a review.
+
+If you've been contributing actively for some time then feel free to open a PR to be added into the contributors list.
+Likewise open a PR/issue to ask for permissions like write access, merge rights or if you want to be added into the technical reviewers:
+
+### Docs and resources
+- [Java Style Guide](JAVA_STYLE.md)

docs/GOVERNANCE/BOARD.md

@@ -0,0 +1,36 @@
+# Governance
+
+Organic Maps Project (organicmaps.app) is an open-source project.
+
+## The Governing Board
+
+The focus of the Governing Board is to assist and guide in the progress and development of Organic Maps, as well as to lead and promote Organic Maps.
+
+The Governing Board is the governing body responsible for the overall oversight of the Organic Maps Project. The Board also has the responsibility to ensure the goals, brands, and marks of Organic Maps and community are protected. The Board serves as the final authority within the Organic Maps Project.
+
+## Governing Board Responsibilities
+
+- Guidance and leadership over the ultimate Project roadmap.
+- Community outreach.
+- Maintenance of health and viability of the community.
+- Maintenance of a healthy and proactive relationship with the Project users and consider those needs and uses in decisions.
+- Coordination of Project messaging.
+- Overall Project leadership as the final escalation point for decisions.
+- Trademark and brand oversight.
+- Appointment of Board Chair.
+- Appointment of new Board members.
+- Re-appointment of Board members after 12 month term of service.
+
+## Chair Responsibilities
+
+- Organize and run the Board meetings.
+- Be the coordinating and lead voice for the Project.
+- Coordinate the Board to set direction and articulation thereof.
+- Focus on helping the Board to reach consensus.
+- Guide the Board in transparency and practicing the open source way in leadership and decision making.
+
+## Current Sitting Board
+
+- [Alexander Borsuk](https://github.com/biodranik)
+- [Victor Govako](https://github.com/vng)
+- [Roman Tsisyk](https://github.com/rtsisyk)

docs/GOVERNANCE/EXPERTS_TEAM.md

@@ -0,0 +1,17 @@
+# Experts and talent
+
+An umbrella "team" for pools of subject matter experts and talent in various fields.
+
+If you need an expert advice in a specific matter like OpenGL, then just tag/mention a relevant group and ask for help.
+If you're an expert in a certain matter and is willing to help the project by sharing your knowledge occasionally then sign up please!
+
+Tag one of these if you seek help/advice on specific matters:
+- @organicmaps/cpp - C++ experts and learners
+- @organicmaps/privacy - privacy best practicies
+- @organicmaps/shaders - 3D graphics and shaders experts
+- @organicmaps/web - web development
+- @organicmaps/brainstorm - general brainstorming of raw ideas
+- @organicmaps/legal - legal matters, licenses compliance
+- @organicmaps/community - community relations, insights into users' feedback and preferences
+
+Please open an issue/PR to ask to be added into one of the pools above or to create a new one!

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](EXPERTS_TEAM.md)
+<br>subject matter experts and talent in different fields, willing to share their knowledge
+
+- [ANDROID](ANDROID_TEAM.md)
+
+- 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