> He may in time still respond but
> because Eduardo is the currently listed maintainer, we should sort out
> who's the active maintainer first before Michael starts working as he
> was indicating he'd like to do it via Locamotion - plus there's the
> issue of signoffs etc.
I guess that active maintainership means, well, being green before
releases, keeping up with the new release cycle, doing sign-offs,
receiving suggestions, correction and modifications and commiting them
to hg and svn, coordinating and translating also the web part of the
localization, reporting bugs for l10n-wide issues, etc. After many
years of this, uninterrupted, I do hope it takes more than a couple of
days of silence to change that status...
First, short answer for Michael Moroni and anybody willing to help with
the Esperanto localization of Mozilla products (yes, please do help!):
Come to:
https://lists.mozilla.org/listinfo/community-esperanto
Follows a longer answer, trying to mention the issues brought up and
some suggestions to move forward:
I've already talked to Michael Moroni a while ago on translations. He
has proposed some changes to existing ones, and some of them (with a
rather big impact, like the global translation for "tab") were accepted.
At the time I filed a set of bugs[1] on his behalf, mentioning his name
and asking him to join the conversation on Bugzilla (he hasn't done that
yet). That is what the current team has been doing, communicating via
bugzilla+patches+irc and it has proven effective so far.
Narro for Esperanto[2] is enabled, but it's been a while (a full
release) since I imported to hg. Michael, how about taking Thunderbird
from there? Usually I ask new contributors to come up with a working
version (because sadly many people have great ideas but not always the
time to pursue them). Maybe you could translate the most exposed parts
of the Thunderbird UI and then the others can check it. I know that a
couple of us use Thunderbird (I do and I'd be willing to check your
translation). But, *before* jumping into administrative rights and
titles, I'd rather see something working first. Maybe you could use the
work of
eozilla.de as a base (try contacting him first).
Michael, keep in mind that what I cannot guarantee, though, is that all
your proposals will make it to the actual product. I know you have
strong views on some issues. There are (sometimes lengthy) discussions
about the correct translations and the outcome does not always leave
everybody happy. For example, I had used for many years a translation
for "bookmark" that was later changed by another that the community
considered more appropriate. I liked the older one better, but that
didn't stop me from commiting the new one.
In you case, this bug[3] (part of [1]) triggered this two set of changes
in hg[4][5] (that should have been noted in the bug report). As you see
your proposal was taken into account. Take for example another good
example of your proposals (langeto/folio), that of bug 784374[6]. It
went right in, globally. No problem commiting it even though there was
at least one reasonable objection to it in Bugzilla.
So, if you want to *propose* modifications (and please consider that
does include the possibly of them being turned down), just keep on doing
it as you were (it'd be good if you filed the bug reports yourself
though, and diffs would be even better). I guess you cannot complain.
But if it is about a specific translation being it just the way you want
it to be ... that's a different story. That's not what maintainership
is for.
That being said, nothing stops anybody from using another tool, feeding
on hg (and/or svn for the web pages), and then sending the patches or
even the full translation either by email or via bugzilla or announcing
it to the newly created email list created with the purpose of making
communication easier (thanks Carlos Valim "Coragem" for that[7]):
https://lists.mozilla.org/listinfo/community-esperanto
Let's go over there and discuss all the issues! Dev-l10n might not be
the right place for it and there are more people willing to contribute
waiting there.
> I think what we've done before is that if the current maintainer doesn't
> respond within a reasonable timeframe that we make the new person
> co-maintainer.
Even maintainers can enjoy a full off-line real-life weekend, can't they? ;)
Friendly, Eduardo.
[1]
https://bugzilla.mozilla.org/show_bug.cgi?id=781833
[2]
http://a.maimult.ro/lmo/projects.php?l=eo
[3]
https://bugzilla.mozilla.org/show_bug.cgi?id=784434
[4]
http://hg.mozilla.org/releases/l10n/mozilla-aurora/eo/rev/cdbac1ca462a
[5]
http://hg.mozilla.org/releases/l10n/mozilla-aurora/eo/rev/35c1140efe41
[6]
https://bugzilla.mozilla.org/show_bug.cgi?id=784374
[7]
https://bugzilla.mozilla.org/show_bug.cgi?id=841571