Move "Mozilla Localizations" to Client Software and enter_bug.cgi

VERIFIED FIXED

Status

()

bugzilla.mozilla.org
General
VERIFIED FIXED
11 years ago
7 years ago

People

(Reporter: Pike, Assigned: reed)

Tracking

Details

Attachments

(1 attachment)

(Reporter)

Description

11 years ago
We're using bugzilla much more for communicating back and forth between localization teams and us or QA resources.
Yet, filing bug on the localizations in our cvs is kind-of awkward, as a bug in a Firefox localization doesn't end up in Firefox, but in "Other Products".
'Client Support' isn't really appropriate anymore for Mozilla Localizations, as they turned into an integrated part of our development.

What I would like to see is that

- Mozilla Localizations shows up on https://bugzilla.mozilla.org/enter_bug.cgi right away, I'd suggest right after Firefox and Thunderbird.
Do we need artwork for that?
- on https://bugzilla.mozilla.org/enter_bug.cgi?full=1, I'd like to see Mozilla Localizations in the 'Client Software' section, at a similar spot as above.

I'm pondering to update the description, too. How does 

For bugs and requests specific to localized versions of Mozilla software (<a href="http://wiki.mozilla.org/L10n:Bugs">more info</a>)

sound?

Comment 1

11 years ago
this isn't something marcia or i can fix
Assignee: marcia → justdave
Component: Bugzilla: Keywords & Components → Bugzilla: Other b.m.o Issues
QA Contact: timeless → myk

Comment 2

11 years ago
Created attachment 239357 [details]
lets use the mozilla dino for "mozilla localizations."  at least to get started...

Comment 3

11 years ago
I'd  rank this listing third since localized versions make up such a high percent of all our downloads.

Maybe change axel's wording a bit to say...

For bugs and requests specific to localized versions of Firefox, Thunderbird, and all Mozilla software.

As axel suggests Point Product Info link to:
http://wiki.mozilla.org/L10n:Bugs

Point bug filing link to:
https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations

Comment 4

11 years ago
we can fix this. however i think this belongs in Components instead of client software. client software is already too big and Mozilla Localizations is not client software in my book.
Assignee: justdave → marcia
Component: Bugzilla: Other b.m.o Issues → Bugzilla: Keywords & Components
QA Contact: myk → timeless
(Reporter)

Comment 5

11 years ago
I don't see any similarities of Localization of our products with Components. People are having problems with Firefox, in a different language. If we want those bugs to get filed properly, the localizations product should be as close as possible to the products as possible. Stripping down Client Software should be a different bug, and I see a bunch of other candidates to go elsewhere, like Grendel or Minimo.
The "pretty list" is not, as far as I know, connected to the Classification that the Product is in. So we could put Mozilla Localizations into the pretty list (third, as chofmann says) without changing its Classification.

Axel: is adding Localizations to the pretty list sufficient, or do you want the full list changed as well?

Gerv
(Reporter)

Comment 7

11 years ago
I think we should do both.
(Assignee)

Comment 8

10 years ago
Is this still wanted?
Assignee: marcia → reed
(Reporter)

Comment 9

10 years ago
Yes.
(Assignee)

Comment 10

10 years ago
Ok, I moved "Mozilla Localizations" to the "Client Software" classification. I'll work on updating the pretty page soon.
Status: NEW → ASSIGNED
(Assignee)

Updated

10 years ago
Component: Bugzilla: Keywords & Components → Bugzilla: Other b.m.o Issues
QA Contact: timeless → reed
(Assignee)

Comment 11

10 years ago
This is staged and ready for the next Bugzilla upgrade.
(Assignee)

Comment 12

10 years ago
This is now live on production.
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
(Reporter)

Comment 13

10 years ago
Verified, thanks.
Status: RESOLVED → VERIFIED
Component: Bugzilla: Other b.m.o Issues → General
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.