If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Localization Process doc needs to be updated

RESOLVED FIXED

Status

Mozilla Localizations
Documentation
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: gueroJeff, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

5 years ago
Process doc on wikimo is outdated and needs updating.

In addition, in light of Khmer community's challenges, some of the doc needs to be explicit about criteria for migrations between release channels.
(Reporter)

Comment 1

5 years ago
Starting at "Starting a L10n effort," you can navigate through the whole process description using the "Next >>" link at the bottom of each page.

It was not written as a tutorial, but as a compiliation of the ideal practices and process we expect the L10n teams to follow. It contains no technical details (as those are contained in the MDN Quick start guide). In addition, it attempts to identify the division of responsibility between the L10n drivers and the L10n communities. Finally, this doc, in combination with the updates I've made to the MDN Quick start guide cover most of the holes (if not all) encountered by the Khmer team.
(Reporter)

Comment 2

5 years ago
Specific doc holes identified through Khmer community's challenges that have now been covered by this and other doc:

- Review, sign-off, and post-sign-off process not clear (should be part of both MDN and wikimo)
    - Part of this doc and written on the MDN (https://bugzilla.mozilla.org/show_bug.cgi?id=728066)

- Migration of L10n builds to various dev stages unclear 
    - Cleared up here on page 3.

- Discrepancies between narro dashboard and hg dashboard, as well as narro export issues with missing files, Linux line endings, etc. 
    - included in intermediate Narro tutorial, as well as technical review doc on MDN (see https://bugzilla.mozilla.org/show_bug.cgi?id=728066 and https://developer.mozilla.org/en/Localizing_with_Narro/Intermediate_tutorial).

- Localizng with Mercurial tutorial on MDN needs to include a common pitfalls section (e.g., missing files, Linux line endings, etc.). This could also be included in an advanced Narro tutorial. 
    - Included in intermediate Narro tutorial, as well as technical review doc on MDN.

- Roles were not clearly defined. Not only does Vannak not know what is expected of him, but even the L10n-drivers did not assume defined roles which lead to a lot of very disorganized communication and contradicting advice, leading all to converge upon Vannak to help him out in a very confusing manner. 
    - Covered in this new Process do. Also working with Arky and Milos to better define roles for specific tasks/milestones, which can then be measured and tracked to assess a new locale's status & progress.

- Other locales were slow to respond when help was requested (or didn't respond at all). New-locales group was only used when Axel asked them to use it. Maybe we need to evaluate its effectiveness.
    - New locales group is pointed to repeatedly throughout this Process doc.
(Reporter)

Comment 3

5 years ago
Adding https://wiki.mozilla.org/L10n:Managing_Assets to Process doc nav path. Currently being drafted and will be ready for review by the end of this week. 

Also added information about the option to release as a language pack, removed references to User Experience review, looked for and edited some of the too flowery language, removed links to l10n-drivers mailing list, fixed breaks in the first page's blocks, and ensured that there was a clear path to the Quick Start guide to answer the "where do I go from here" question.
Status: NEW → ASSIGNED
(Reporter)

Comment 4

5 years ago
Finished first draft of L10n:Managing_Assets. Added paragraph to https://wiki.mozilla.org/L10n:Localizing_a_project#Localizing_Firefox about creating and using L10n assets, linking back to the L10n:Managing_Assets page. Will request review tomorrow.
(Reporter)

Comment 5

5 years ago
Closing bug. Any future revisions can be done outside of this.
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.