938195 - Rename Mozilla Localizations :: Other to "Coordination"

Status: RESOLVED INCOMPLETE

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

Description

[Gordon P. Hemsley [:GPHemsley]]

(This is similar to bug 788352.)

Nowadays, it seems like Mozilla Localizations :: Other is used mostly to coordinate issues that apply to multiple locales, including requests for the localization of new marketing content.

It seems to me that "Other" (and its description of "Other translations.") is not the best way to advertise the real use and purpose of the component.

As such, I recommend renaming it to "Coordination" (or "Multi-locale Coordination") and updating the description to be more, well, descriptive. Perhaps something as simple as "Bugs for coordinating tasks and issues across multiple locales."

Axel, I know you had some issues with my last proposal, but I hope you'll revisit this with a fresh and open mind. :)

Comment 1

[Liz Henry (:lizzard) (relman/hg->git project)]

How about adding a component called "Mozilla Localizations::Coordination" with that description? Would that be useful? Then we'd still have a catch-all "other" component, if people want that to persist.

Comment 2

[Gordon P. Hemsley [:GPHemsley]]

I'm not convinced that the "Other" component as it pretends to be serves any purpose anymore. Anything involving new locales would fit in either "Coordination" or "Registration & Management", IMO.

Comment 3

[Axel Hecht [:Pike]]

"Other" is still used for localizations that don't have a bugzilla component. Most often, bugs don't stay there for long, but the component still serves its purpose.

I'm not sure we need a "tracking" in the l10n product, maybe we can make use of a "l10n" in the Tracking product?

Comment 4

[Gordon P. Hemsley [:GPHemsley]]

(In reply to Axel Hecht [:Pike] from comment #3)
> "Other" is still used for localizations that don't have a bugzilla
> component. Most often, bugs don't stay there for long, but the component
> still serves its purpose.

I watch the "Other" component, and I don't recall getting bugmail about such bugs. Could you point to a few recent ones that fall into that category?

(And I still think such bugs are better suited for "Registration & Management", anyway.)

> I'm not sure we need a "tracking" in the l10n product, maybe we can make use
> of a "l10n" in the Tracking product?

I suppose that could work, but then it would empty "Other" of a lot of its existing bugs.

Comment 5

[Axel Hecht [:Pike]]

All bugs we file for new localizations start out in "Other", and we haven't started new localizations for a while. the latest was Xhosa, which had a bugzilla component already from previous lives.

Also, I don't agree that those should be in Reg & Man.

Comment 6

[Gordon P. Hemsley [:GPHemsley]]

(In reply to Axel Hecht [:Pike] from comment #5)
> All bugs we file for new localizations start out in "Other", and we haven't
> started new localizations for a while. the latest was Xhosa, which had a
> bugzilla component already from previous lives.

If that's the case, then I see no reason why we can't change that behavior.

> Also, I don't agree that those should be in Reg & Man.

I'm curious to why, because otherwise I don't know what falls under the "Management" part.

Comment 7

[Gordon P. Hemsley [:GPHemsley]]

I just found that the "Other" component was created by bug 210549 (in 2003) specifically because some locales didn't have components and people didn't know where to file bugs on those locales.

I don't think this is a problem anymore, given how trivial it is to create a new component for a new locale. (It's part of the new locale setup process already, isn't it?)

Comment 8

[:glob ✱]

tagging as needinfo to indicate that this request is still under discussion and we can't take action until a decision is reached.

Comment 9

[Axel Hecht [:Pike]]

This discussion is now in mozilla.dev.l10n.

Comment 10

[Axel Hecht [:Pike]]

OK, needs info from me, then. bad glob, fixed all the useless flags going nowhere, I guess ;-)

Comment 11

[:glob ✱]

closing stale bug, please re-open when a decision has been made.