Confirmed users
1,276
edits
L10n:Driving: Difference between revisions
Jump to navigation
Jump to search
→The process
No edit summary |
|||
| Line 4: | Line 4: | ||
# Make sure project owners follow the [[L10n:NewProjects|instructions for getting their projects localized]]. | # Make sure project owners follow the [[L10n:NewProjects|instructions for getting their projects localized]]. | ||
# Document important procedures, se wo can carry on the project in case someone goes on holiday, etc. | # Document important procedures, se wo can carry on the project in case someone goes on holiday, etc. | ||
# Release cycle of the project should give localizers enough time to finish their work before each release. It depends on the number of new strings for each release, but we usually aim at 2 weekends minimum. | |||
# Review English source strings. | # Review English source strings. | ||
#* You have a good chance of catching obvious errors, which will make you break the string freeze if you don't fix them in time, which requires extra communication, PO extracting, Verbatim juggling etc. | #* You have a good chance of catching obvious errors, which will make you break the string freeze if you don't fix them in time, which requires extra communication, PO extracting, Verbatim juggling etc. | ||
| Line 9: | Line 10: | ||
#* Project owners should request a review by QA. | #* Project owners should request a review by QA. | ||
#* [[User:Jbeatty|Jeff]] is also happy to help. :-) | #* [[User:Jbeatty|Jeff]] is also happy to help. :-) | ||
# | # Reach out to localizers on the appropriate mailing lists ([http://groups.google.com/group/mozilla.dev.l10n.announce/topics dev-l10n-announce], [http://groups.google.com/group/mozilla.dev.l10n.web/topics dev-l10n-web], [http://groups.google.com/group/mozilla.dev.l10n/topics dev-l10n]). | ||
#* Get a decision process triggered in the communities and a commitment to follow up. | #* What is the project about? | ||
#* Statistics: we need a descent status for the project across locales, localizers need motivation. | #* How many strings and/or words are to be localized? | ||
#* We don't want to look like we're imposing projects onto communities. | #* When is the deadline and what does the release cycle look like? | ||
#* In Verbatim, adding 100 locales means clicking 100 times to add each one separately. | #* Web projects: where is the staging server available for localizers to review their work? | ||
#* Where can localizers opt in: [https://l10n-stage-sj.mozilla.org/webby/ webby] or the mailin list? Do not give them access to strings automatically, there are several reasons for this: | |||
#** Get a decision process triggered in the communities and a commitment to follow up. | |||
#** Statistics: we need a descent status for the project across locales, localizers need motivation. | |||
#** We don't want to look like we're imposing projects onto communities. | |||
#** In Verbatim, adding 100 locales means clicking 100 times to add each one separately. | |||
# Extract strings and merge them with existing translations. | # Extract strings and merge them with existing translations. | ||
#* [http://svn.mozilla.org/projects/l10n-misc/trunk/browserid/README README] file on how to run the scripts will come in handy. | #* [http://svn.mozilla.org/projects/l10n-misc/trunk/browserid/README README] file on how to run the scripts will come in handy. | ||
| Line 19: | Line 25: | ||
#* Decide if you want to break the string freeze or move them to the next release. | #* Decide if you want to break the string freeze or move them to the next release. | ||
#* Connect localizers' requests with project owners or change strings in the codebase on your own. | #* Connect localizers' requests with project owners or change strings in the codebase on your own. | ||
# Prepare the list of shipping locales for project owners. | # Prepare the list of shipping locales for project owners. | ||
#* Make sure that localizers are aware of the shipping policy (do we ship incomplete locales?). | #* Make sure that localizers are aware of the shipping policy (do we ship incomplete locales?). | ||
| Line 25: | Line 30: | ||
#* In Verbatim, a [https://etherpad.mozilla.org/localize-browserid-shipping script] can be used to get the list of fully localized locales. | #* In Verbatim, a [https://etherpad.mozilla.org/localize-browserid-shipping script] can be used to get the list of fully localized locales. | ||
#* In Verbatim, some locales might be at 100%, but they forget to commit to VCS. Identify such locales with the help of a [https://github.com/mozilla/browserid/blob/dev/scripts/check_po.sh script]. | #* In Verbatim, some locales might be at 100%, but they forget to commit to VCS. Identify such locales with the help of a [https://github.com/mozilla/browserid/blob/dev/scripts/check_po.sh script]. | ||
== Working with Verbatim box == | == Working with Verbatim box == | ||