672121 - Mark as ready for localization a major content change

Status: RESOLVED INVALID

(support.mozilla.org :: Knowledge Base Software, task)

Description

[Scoobidiver (away)]

When an article is approved as a major content change that needs immediate translation, mark it as ready for localization.
See the warning at the top of https://support.mozilla.com/fr/kb/est-ce-que-firefox-fonctionnera-sur-appareil-mobile

Comment 1

[Ricky Rosario [:rrosario, :r1cky]]

We should probably not show the warning in this case. Magically changing the revision to ready for l10n doesn't seem like the right thing to do (better to be explicit). Or maybe show yet another warning if the reviewer selects major and doesnt check the ready for l10n checkbox?

Comment 2

[James Socol [:jsocol, :james]]

I'm with Ricky: the whole point of ready-for-l10n was to be explicit. A warning if you select major makes sense.

Comment 3

[Scoobidiver (away)]

Be aware that this change will give reviewers ready-for-l10n rights for major content changes which were initially only for administrators.
Reviewers won't still have ready-for-l10n rights for normal content changes.

Comment 4

[Verdi [:verdi] Best to slack me]

We don't want to do this. Major content changes and ready for L10n are two different things. If an article has information that is no longer correct, it can be changed quickly with one revision but then a few more minor changes could be needed to get it ready for L10n.

Comment 5

[Scoobidiver (away)]

(In reply to comment #4)
> We don't want to do this.
If you don't wish unwanted bugs, answer to threads that highlight dysfunctions, https://support.mozilla.com/forums/contributors/707087 in this case.

> it can be changed quickly with one revision
See https://wiki.mozilla.org/Support/Article_Tracking#All_Articles and sort the notes column by "Ready for localization?". No articles have been marked ready for localization since June 21 once they have been approved.
See also http://www.thefreedictionary.com/quickly

Comment 6

[Kadir Topal [:atopal]]

Scoobie, there is a reason why no article was marked ready for l10n: The messaging system for that feature wasn't ready yet. All the remaining necessary parts will be pushed to production today. 

Also: we specifically said that we will mark articles as ready for L10n after the second week of the beta period, which is: This week :)

Comment 7

[Scoobidiver (away)]

(In reply to comment #6)
> we specifically said that we will mark articles as ready for L10n
> after the second week of the beta period, which is: This week :)
I agree for the 5 Firefox 6 articles (https://wiki.mozilla.org/Support/Article_Tracking#Updates_for_Firefox_6) but not for the 16 articles that contain wrong information about the current version (https://wiki.mozilla.org/Support/Article_Tracking#All_Articles).

Per comment 4, I close it as invalid.