It is the responsibility of the active community maintenance team for each
active locale to keep up-to-date with reviews of pull requests and handling
issues filed against that locale. You can filter the relevant pull requests and
issues for each locale using the relevant label — l10n-fr, l10n-ja, l10n-ko
, l10n-pt-br, l10n-ru, l10n-zh and l10n-es.
Active community maintenance teams are expected to keep their locales maintained and reasonably up-to-date. This means:
- Reviewing and actioning all pull requests within 2 weeks.
- Triaging and fixing all actionable issues within 1 month.
- Making reasonable progress on keeping MDN’s Tier 1 content (definition TBD)
synchronized with the
en-USversions. This means some progress should be made each week, e.g. updating an article to be in sync with the English version, removing or fixing a bad quality article…
If no progress is made on a locale in these areas within 1 month, the locale will be considered inactive, and edits will stop being accepted.
The review teams for each locale are:
- Brazilian Portuguese (
pt-BR) content — the @yari-content-pt-br team, which consists of: - French (
fr) content — the @yari-content-fr team, which consists of: - Japanese (
ja) content — the @yari-content-ja team, which consists of: - Korea (
ko) content — the @yari-content-ko team, which consists of: - Russian (
ru) content — the @yari-content-ru team, which consists of: - Chinese (
zh-CNandzh-TW) content — the @yari-content-zh team, which consists of: - Spanish (
es) content - the @yari-content-es team, which consists of:
Periodically we synchronize all the localized document tree structures with the
en-US tree structure (English slugs only), to make the documentation easier
to manage. When documents are removed from en-US it results in orphaned
documents within a sub-directory of each locale folder.
Active locale maintenance teams are invited to spend some time exploring the orphaned documents, to see whether any of this work is worth keeping (either adding to, or merging with an existing document in, the main tree), or whether it can just be deleted.
When a synchronization occurs maintenance teams are given two weeks to decide what to do with the affected documents in their locales to keep things in sync.
Note: Conflicting docs are often created during the sync operation when en-US
documents get merged — for example if Foo/Bar becomes just a section inside
Foo, and we redirect Foo/Bar to Foo#Bar. This will result in a conflict
as the sync job tries to move the translated Foo/Bar to Foo according to the
redirect, but Foo already exists.
To activate a locale you must apply with the following information:
Please specify which of the following two locales you wish to have unfrozen:
- German (de)
- Polish (pl)
NB These are the only frozen locales we will consider - see The future of MDN localization in this Hacks post
You need to put together a community maintenance team. This requires:
- A team lead who will be the communication point between that team and the MDN core team, and have overall responsibility for the team.
- At least two other members, so that members can review other members work.
- A place to discuss this team's localization work. This can be a Telegram group, Matrix chat room, or whatever the team thinks is best.
To find out more about our existing teams see Review teams above.
Please indicate that you agree to our Requirements for keeping locales up-to-date above.
Also indicate that your team agrees to adhere by our Code of Conduct and License (see below)
If the application is been successful you can start work on your locale. See the guidelines for set up in the README.
You can add your team to the localizing MDN page.
If you want to ask questions or talk to us about forming a new community maintenance team, see ask for help.
Everyone participating in this project is expected to follow our Code of Conduct.
When contributing to the content you agree to license your contributions according to our license.