Closed Bug 986246 Opened 11 years ago Closed 9 years ago

[L10N] Update Content Review Guidelines (Hindi)

Categories

(Tracking :: User Story, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: cgalimidi, Assigned: teoli)

References

Details

User Story

Language: Hindi
Target Launch: 1-August


Updated Content Review Guidelines (currently on MDN)  (janet swisher, Jérémie Patonnier at <jeremie@patonnier.net>)
URL: https://developer.mozilla.org/en-US/Apps/Publishing/Marketplace_review_criteria
language :: hindi
Assigning it to Jean-Yves.
Assignee: pmo → jypenator
Hi ! In order to assess the work, is there an expected date where this need to be translated?
Flags: needinfo?(cgalimidi)
Blocks: 991206
No longer blocks: tarako-marketplace
Flags: needinfo?(cgalimidi)
For marketplace, Hindi is our highest priority L10N work for the forseeable next 4-6 weeks. The Marketplace, in Hindi would first be exposed to external partners in approx 6-8 weeks. We would hope by the end of May a good portion of the Marketplace localization could be accomplish.
User Story: (updated)
The Marketplace Review Criteria are available in hi-IN (since a few weeks now): https://developer.mozilla.org/hi-IN/docs/Mozilla/Marketplace/Submission/Marketplace_review_criteria I don't know if there are other things covered by this bug.
Flags: needinfo?(jypenator)
Summary: [L10N] Add new localization (Hindi) to Marketplace & Update Content Review Guidelines → [L10N] Update Content Review Guidelines (Hindi)
Need info from Karen / Mika - Must ensure that external / consultant legal counsel personnel are translating these documents. (Cannot be internal Mozillians or non-legal personnel)
Ali - Looking to get the Marketplace Content Review Guidelines localized. These need to happen on a timely basis w/ go to market launches for FxOS. This doc used to be localized when it was part of the Marketplace repositories. Should we move it back there to get these completed? What is your recommendation? Caitlin PS. Please disregard comment 9 - accidental update.
Flags: needinfo?(jypenator) → needinfo?(aspivak)
Question: how did these docs get localized when they were part of the Marketplace repositories? Were they baked into the launch process? Who did the translations - do we hire a company with the correct background (from comment 6 above)? The translators you need are likely not hooked into the process of translating on MDN. Current MDN localizations are done by volunteers, and we don't necessarily have volunteers who work on MDN who know that language and have the background requested above. Our volunteers also work on their own schedule, so it's not always easy to get things done on a particular timeline. I am not married to these docs being in one location or another - we can always link to them wherever they are. I'd rather we figure out where the process is broken and how to address as quickly and easily as possible.
Flags: needinfo?(aspivak) → needinfo?(cgalimidi)
Marketplace L10N is also done by volunteers, with the same structure. Peiying Mo manages the Marketplace L10N Community. Rule of thumb, we don't support docs on Marketplace, and MDN should be the location. Let's you & I touch base with Axl and team - Let's find / fix the break.
Group: mozilla-employee-confidential
Flags: needinfo?(cgalimidi) → needinfo?(l10n)
Marketplace localization is managed by volunteers, legal documents are localized by external council and eventually reviewed by the Community (process is managed by Pei). Given the status of Marketplace for hi-IN, I doubt this page was localized there. My guess, by looking at the history, is that it was simply localized on MDN by a volunteer https://mozillians.org/it/u/khushal704/ And to be honest it's the first time I see this page as a requirement in over a year of Fx OS launches. So, what is exactly the question there?
Flags: needinfo?(l10n)
This is no more on priority. Hence closing this one.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.