466225 - Facilitate localization changes in DOM Inspector

Status: NEW

(SeaMonkey :: General, defect)

Description

[u162289]

dom-inspector/resources/locale should have Hg write access for localization teams as it is the case for the other extensions provided with SeaMonkey or should be moved to l10n-central/ab-CD/extensions/ .
Currently, each locale has to open a bug to commit localization changes...

Comment 1

[Axel Hecht [:Pike]]

Frankly, none of the SeaMonkey localizations are working in l10n-central. The only things in extensions that are really working are spellcheck and reporter, neither of which is really an extension.

It's up to the owners of dom-inspector if they want to grant localizers write access to that repository, IMHO.

In general, I'd prefer to see a rather complete description of the scenario before talking about path locations and then possibly derive a scenario from that.

Comment 2

[u162289]

Ugh : I asked a question to Seth on #l10n a few minutes ago, he didn't answer and you answered in this bug?
Axel, I know this is out of your scope.
I think DOMi is out of scope for MoCo or Mozilla Messaging. So whom scope is it? Mozilla Foundation?
I don't care as a localizer of whom can handle this, if nobody can handle this, just state this in .l10n, full point.
There are currently 2 or 3 locales I think.

If Mozilla "WhateverOrganization" can't deal with this, just say it!
As a friendly reminder, I just recall you that, as Mozilla benevolent contributors, we haven't necessarily got skills, wills, time or authority to handle with this (Axel, this is not targeted to you of course, but to the project managers ;) ).

Regards

Comment 3

[Seth Bindernagel]

(In reply to comment #2)
> Ugh : I asked a question to Seth on #l10n a few minutes ago, he didn't answer
> and you answered in this bug?

Cedric, I believe I answered in IRC, but perhaps it didn't go through. 

> Axel, I know this is out of your scope.
> I think DOMi is out of scope for MoCo or Mozilla Messaging. So whom scope is
> it? Mozilla Foundation?

I've been asking today who is the owner of DOMi.  I hope to give you a good contact and start a conversation tomorrow with all of us.

Comment 4

[Shawn Wilsher :sdwilsh]

I've been the acting module owner of the DOMi for about two years now.  The policy during that time has been rs=sdwilsh to land the changes as long as one of two conditions were met:
1) the change has been reviewed by the locale qa contact
2) the change was made by the locale qa contact

The spirit of these policies were to simply make sure that it wasn't some random contributor trying to change stings.  I'm assuming that folks who have access to the l10n repos have been vetted by someone, so I'm fine with them having access to update locales.  I just ask that they make sure to not break the build by adding themselves to the Makefile.in and not have a full locale.

Comment 5

[u162289]

Maybe I don't have all the information, but I thought DOMi might be handled like ChatZilla which is also provided with SeaMonkey, regarding localization:
It is located in l10n-central/ab-CD/extensions/irc .

Currently, when there is a new string in ChatZilla, I don't think the owner has to sweep the Makefile.in and localizers don't have to provide a patch for Makefile.in when they update their strings.

Giving access to localizers in dom-inspector/resources/locale only (if this is doable), doesn't solve the problem of the Makefile.in: it remains the "pain" for Shawn to review patches for each locale and for localizers to open a bug and provide a patch.

The other solution to put the locale part in l10n-central/ab-CD/extensions/inspector would be ideal as the localizers would have only to deal with l10-central.
I guess there are many technical reasons that would make this difficult, like the building.
The difference between DOMi and ChatZilla is that ChatZilla still resides in CVS I think.

Nonetheless, I remember that some time ago, the locale part of inspector was in the l10n repos, I didn't understand at that time why it has been moved into the code repo.

Because of the current process, there are only 3 locales + en-US currently for DOMi though there are many more locales that provide SeaMonkey.
As a result, some localized SeaMonkey builds are provided with Inspector in English.

Another point, maybe this is a job for SeaMonkey drivers to handle?

Comment 6

[Axel Hecht [:Pike]]

As I tried to say before, the SeaMonkey extensions don't really work as optional extensions yet. "extensions" is the word I missed in comment 1. That includes irc, venkman, and dom-i. Any of these need manual maintainance of which locales they build to not break. 

The problems there are really independent on the location of those files in version control.

To answer your question about the scope of DOM-I, none of the orgs really matter, AFAICT, it's the module owners who need to propose, and implement, something. Which, AFAICT, are sdwilsh, and to some extent the SeaMonkey council.