mozilla-l10n / documentation Goto Github PK

Need to document the process to add locale to production for mozilla.org

• Create a new repository
• Move existing user facing documentation to this repository

Install + screenshots

Store document in /common, shared instructions for Desktop and Android

Work is being done in bug 1352539, and affects both mobile and desktop.

@Delphine
I'll start staging an update to our docs, and ask for review when ready. This is mostly an heads-up, because I know there is some work pending.

Right now we go into way too many details in too many docs.

At some point the process will change, dropping MozReview, and that will require updating all of them. Better to consolidate that information in one document beforehand.

Webapp is disabled, we should clean up our documentation.

OS support

MozReview is becoming deprecated on August 6

We're sunsetting™ the webdashboard, and we should clean up our documentation as much as possible.

New doc.

How to remove obsolete files we are certain are no longer relevant or useful? Recent example is the removal of FFOS files on mozilla.og.

Follow the example of documents written about dropping locales for other projects.

New document.

Should include:

• Prerequisites (font, locale, CLDR support)
• Link to existing single/multi locale docs, when to add to which one
• Check to make sure that language appears in multilocale build the next day (https://bugzilla.mozilla.org/show_bug.cgi?id=1263437)

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please see Mozilla-GitHub-Standards or email [email protected].

(Message COC001)

That bug is moving all files in a different position, need to update our docs.

Update all Firefox and Firefox for Android documents to reflect the process and technical changes with implementing x-channel.

Includes:

• l10n.toml file (project configuration) when adding new locales

https://mozilla-l10n.github.io/documentation/products/android_l10n/index.html
https://mozilla-l10n.github.io/documentation/products/android_l10n/adding_new_locales.html

Both pages show up blank. I need to check locally what's going on.

@Delphine
Can I also shorten the sidebar link to Adding new locales?

See https://bugzilla.mozilla.org/show_bug.cgi?id=1461345

We need to reorganize the docs repo to reflect the new structure we agreed upon in Mountain View. That can be found here:

For both localizers and l10n-drivers

Once #23 is fixed, we should simplify existing instructions by only explaining how commands work only in the VM scenario.

The productization document is going to be updated and unified at the same time, but the other docs need an update.

See https://bugzilla.mozilla.org/show_bug.cgi?id=1422249

We need to update the documentation:

• When adding a new locale, it needs to be added to exclude-multi-locale
• When moving it to beta, it needs to be removed from that list

Onboarding steps/requirements are currently found here: https://docs.google.com/document/d/1QaWvV6IrpUKMzUlerpduG-ctLQ4u__9xk2G0dY8SawU/edit# . This document will be an official version of the content here and used as a guide for l10n-drivers to onboard Mozilla cost centers.

This is an issue to test how Projects work in GitHub.

• First action item
• Second action item

We should wait for the project to be completely disabled in Pontoon, and comms out to localizers. But once that's done, we should remove the appstores section https://mozilla-l10n.github.io/documentation/products/appstores/index.html

#167 takes care of the tools part.

Each repository on GitHub has an option to add a description and a link. It would help to add https://mozilla-l10n.github.io/documentation/ as a URL link to make it faster to switch from the repository to the documentation view.

• https://docs.google.com/document/d/1gCDX7i-pLUYiGKt20Se4m3BLAIGUOb9hKpjcBfmbOaI/edit#
• https://wiki.mozilla.org/L10n:NewProjects

Topics:

• Where to find changesets
• Type of issues to look out for
• Sign off in x-channel world

Content to come from here: https://docs.google.com/document/d/1gCDX7i-pLUYiGKt20Se4m3BLAIGUOb9hKpjcBfmbOaI/edit#

Add to documents covering adding locales for these projects:
[ ] Fx iOS
[ ] Focus

Templates for messages that we regularly send out to localizers, vendors, internal teams, etc.