Closed Bug 670460 Opened 14 years ago Closed 13 years ago

Delete or disable South African component in Mozilla Localizations product

Categories

(bugzilla.mozilla.org :: Administration, task)

Production
task
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: GPHemsley, Assigned: dkl)

Details

The South African component in the Mozilla Localizations product was created in bug 350551. As far as I can tell, it was only ever used for 3 bugs before each South African language/dialect got its own component. Two of the bugs in the South African component (bug 366424, bug 368671) were specific to Afrikaans, so I moved them to that component. The remaining bug (bug 350462) is a single tracking bug for shipping Firefox 2 in all the South African locales. It seems kinda silly to keep a component around for a single, really old bug. It seems like it'd be better to just move that one bug to Other or something and delete or disable the component. At the very least, it should be renamed to use a capital 'ZA', as it's a region code, not a language code. (The language code 'za' refers to the Zhuang / Chuang macrolanguage.) It's also, AFAICT, the only l10n component for a region, rather than a langauge or dialect, which further makes it unusual.
(In reply to comment #0) > The remaining bug (bug 350462) is a single tracking bug for shipping Firefox > 2 in all the South African locales. > > It seems kinda silly to keep a component around for a single, really old > bug. It seems like it'd be better to just move that one bug to Other or > something and delete or disable the component. I realized that it's not uncommon to have multi-locale bugs in the Other component, so I just went ahead and moved it. The South Africa component should now be completely empty.
We'll do here what Dwayne and his teams want. Gordon, as much as I appreciate your passion here, it's not appropriate to make a call for another community.
Assignee: nobody → dkl
Status: NEW → ASSIGNED
Should I go ahead and delete the component or is there a way to find out what the decision is from the community responsible for the component? The other option would be to just leave it and close this bug.
(In reply to comment #3) > Should I go ahead and delete the component or is there a way to find out > what the decision is from the community responsible for the component? The > other option would be to just leave it and close this bug. Barring community approval, at least rename it so that it uses capital 'ZA'.
(In reply to comment #4) > (In reply to comment #3) > > Should I go ahead and delete the component or is there a way to find out > > what the decision is from the community responsible for the component? The > > other option would be to just leave it and close this bug. > > Barring community approval, at least rename it so that it uses capital 'ZA'. Renamed to ZA.
It has worked fine with the current 4 South African languages to have bugs against the language. As we focus on a number of languages it is not uncommon that we have the same error across all our locales. That would be the only instance where this could be useful. Also productisation bugs are usually the exact same for all the locales in ZA. But if that is solved with individual bugs and a tracking bug then that works for us. So I guess that means delete this. We'll do it on a language level and if needed create a tracking bug for common issues.
Per comment 6, this can probably be deleted. I don't think there's been any additional need for the component in the year since I originally filed this bug. David, I think you can go through with the deletion.
Thanks. Deleted.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.