Looking at a l10n bugzilla classification
07.26.10 - 01:44pm
We intend to move from components per locale in the “Mozilla Localizations” product to a matrix of products per locale, and components for each of Firefox, Thunderbird, et al. I’ve created an add-on to set up the products and components and laid out in the newsgroup thread. I wanted to share some screen shots on how things look locally now.
enter_bug.cgi?classification=Mozilla in Your Language looks like this:
Localizers can edit the descriptions on localize.m.o. I’m not totally convinced that the current formatting of the products are great. The double () braces disturb me, both here and on the actual bug form (see below). I might prefer “l10n:ab-CD Language (Region)”.
This is the actual bug entry form, and shows the localized component description. It also shows a rather confusing line wrapping of the product name.
Another aspect that we were concerned about was how it’d look if you changed the product of a bug. Locally, this looks like this now:
Got comments? Please leave them in the original newsgroup thread, or here.
Hmm. So this will cover all products? That will make it a little harder to watch all localization for a particular product, but I don’t know how common of a need that is.
Why not take the “l10n: ” off the front of the product names, since they’re all obviously l10n now?
Hi,
Some locales have their own Bugzilla installation. It might be nice to add the URL of the fully localized community Bugzilla installation prominently, somewhere (in the most efficient place, no idea where this would be :\ ).
Cédric
Regarding your first question, there’s a cross-locale alias alas all@firefox.localization.bugs that’s on default CC for the components.
The l10n: prefix is to group all localization components together when moving a bug from one product to another, so that folks can easily skip it. That’s because one can’t move the bug from one classification to another, AFAIK, right?
Cedric, not sure if that’s the same thing.
Like, a separate bz install couldn’t have bugs blocking a release, or a tracking bug, and won’t generally show up in bugzilla queries.
That doesn’t mean that having your own bz install is a bad idea, but I don’t see an obvious way to integrate the installs.
This is cool. I agree “l10n:ab-CD Language (Region)” would look better, and is as rational a way to sort as any.
One correction – ga-IE is “Irish” not “Gaelic”.
Kevin: Oops, sorry, I didn’t check my notes on a ton of languages. I’ll make sure the final products have their names right.
Axel,
You can move a bug from a product being in one classification to another product being in another classification. Bugzilla has no restrictions in this area.
Ah yeah, we should group the product by Classification. I think there’s a bug for that already. Would require some refactoring first.
-Max
LpSolit, sorry, I wasn’t clear there. What I meant to say was:
When moving a bug from one product to another, you can’t restrict that to a classification, or you can’t take a bug in “Client Software” and move it to some product in “Mozilla in Your Language” explicitly. Just implicitly by moving it from a product in one to a product in another. The additional taxonomy we have on products doesn’t help us there.
See also mkanat’s comment, who read what I wrote to say what I meant :-)
“Ah yeah, we should group the product by Classification. I think there’s a bug for that already.”
Yep, there is one: https://bugzilla.mozilla.org/show_bug.cgi?id=539894 :) (just for reference)