788352 - Rename Mozilla Localizations > Other to "Tracking"

Status: RESOLVED WONTFIX

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

Description

[Gordon P. Hemsley [:GPHemsley]]

It seems the primary reason for the the Mozilla Localizations > Other component nowadays is to track multi-locale localization efforts. It would probably be best to have the component name and description reflect that.

Product: Mozilla Localizations
Component: Tracking
Description:
This component is used for bugs tracking changes across multiple locales.

Axel, Pascal, is that alright with you?

Comment 1

[Axel Hecht [:Pike]]

The most frequent use of "Other" is to file bugs on localizations that don't yet have their own bug structure, notably, new localizations.

I don't think that "Tracking" makes sense for those.

The bugs that stick in "Other" might be kinda-tracking, but I'm not seeing the value of them being renamed ad-hoc..

Resolving this WONTFIX, unless there's good reason to reopen.

Comment 2

[Gordon P. Hemsley [:GPHemsley]]

(In reply to Axel Hecht [:Pike] from comment #1)
> The most frequent use of "Other" is to file bugs on localizations that don't
> yet have their own bug structure, notably, new localizations.
>
> I don't think that "Tracking" makes sense for those.

I don't think the data supports that claim:
https://bugzilla.mozilla.org/buglist.cgi?list_id=4279868;component=Other;product=Mozilla%20Localizations;classification=Client%20Software;query_format=advanced

Pretty much all of the bugs filed in this component in the last two years are tracking bugs per comment 0.

There aren't many bugs related to new localizations in this component. New registrations go in the Registration & Management component, and I believe it's trivial to request the creation of a new Bugzilla component for any new localization that gets approved, so there is little need for a place dedicated to "lost" localizations.

> The bugs that stick in "Other" might be kinda-tracking, but I'm not seeing
> the value of them being renamed ad-hoc..

If you ask me, I'd say the name "Other" is more ad-hoc than the name "Tracking", given the data.

> Resolving this WONTFIX, unless there's good reason to reopen.

Well, you know where I stand on this, but I'll await your reply.

Comment 3

[Axel Hecht [:Pike]]

The data of existing bugs isn't really representative, as we're moving the bugs out of "Other" as soon as we have appropriate components created.

Also, Tracking would imply that anyone tracks these bugs, which isn't happening.

Comment 4

[Gordon P. Hemsley [:GPHemsley]]

(In reply to Axel Hecht [:Pike] from comment #3)
> The data of existing bugs isn't really representative, as we're moving the
> bugs out of "Other" as soon as we have appropriate components created.

I curious—what types of bugs do these wind up being? Is there a reason why you can't wait until the component is created before filing them? (Perhaps, by requesting the new component earlier in the process?)

> Also, Tracking would imply that anyone tracks these bugs, which isn't
> happening.

I'm not really sure what you mean here. The idea here was modeled off of Core > Tracking, where tracking bugs have their own component.

Would it make more sense to create a new component for tracking, instead?