Files
comaps/docs/TEAMS.md
Konstantin Pastbin e3e4a1985a Organic Maps sources as of 02.04.2025 (fad26bbf22ac3da75e01e62aa01e5c8e11861005)
To expand with full Organic Maps and Maps.ME commits history run:
  git remote add om-historic [om-historic.git repo url]
  git fetch --tags om-historic
  git replace squashed-history historic-commits
2025-05-08 21:10:51 +07:00

3.5 KiB

Teams

Organic Maps is led by community contributors, with functional domains occasionally establishing or dissolving their leadership structures, formal or informal. This file outlines the functional project structure that has evolved over time. The current list of teams is available on GitHub, accessible only to GitHub Org members due to the limitations of GitHub.

Teams are typically assigned as code owners for certain sections of the repository. GitHub will automatically request a review from the responsible team when changes are made to the relevant part of the repository in a pull request. See the CODEOWNERS file for more information. Please feel free to tag the relevant team in the comments if you need assistance in a specific area. If you are unsure which team to contact, please tag @organicmaps/triage for help.

Triage

People who help with triaging incoming issues and pull requests. Tag this group if you are unsure which team to tag.

Mergers

People who can merge pull requests that are ready.

Android

Android experts.

Android Auto

Android Auto experts (a subteam of Android).

iOS

iOS experts.

Qt

Qt Desktop & Convergent UI experts.

C++

C++ experts.

Rendering

Rendering experts.

Data

Map data generation team.

Styles

Map styles team.

DevOps

DevOps team.

Design

Visual design (icons, graphics, colors, contrast, etc.).

Web

Web development experts.

Growth

Marketing, ASO, SEO, and SMM experts.

Product

Product management group.

Translations

Internationalization and localization.

Tag @organicmaps/translations-langcode (e.g. @organicmaps/translations-fr) for specific language.

Support

End-user support: feedback in stores, emails, user-facing docs (FAQs).

Legal team.