launchpad-translations-coordinators team mailing list archive

[Danilo Šegan <danilo@xxxxxxxxxxxxx>]

Hi Adi,

У суб, 27. 12 2008. у 11:23 +0200, Adi Roiban пише:
> 
> Everyone (both admins and members) from
> "launchpad-translators-leaders"
> team can assign teams for Launchpad Translators translation group?
> As far as I see the answer is yes. Can we restrict only to team
> admins?

No, that's why the team is named "-leaders" and not "-coordinators": I
see why you wanted it renamed now.  What we want to do instead is set up
a separate launchpad-translators team (no need to limit it to only team
coordinators), and post announcements and have discussion there.

> I don't know how the rosetta administration works but maybe we will
> need one group for administration  "launchpad-translators-admin" and
> another group for coordinators "launchpad-translators-coordinators"

Yeah, basically, except that I'd keep the "-leaders" team and open up
entirely new team for anyone interested in notices.  Coordinators would
be required to participate.

> Like i said above I don't know if you are ok with using
>  launchpad-translation-leaders mailinglist for this.
> As joining the mailinglist requires to be a member of the team, and
> being a member of the team you are admin for Launchpad Translators
> group in Rosetta.

IMHO, we should have a generic translation list open for everybody to
participate in.  This should include discussions about both translation
standards and launchpad translators group. It's also the place we'd sent
announcements to.  If traffic turns out to be huge, we can set up a
separate announcement mailing list later.

However, I was under the impression that we wanted to use
ubuntu-translators list for the time being.

> I still don't know how we should decide who we appoint for a specific
> language. 
> I don't want to create a complicated process for appointing new
> languages and teams and creating a high entry barrier, but in the same
> time we must assure the quality.

It's simple.  You check:

  1. A person owning the proposed team has already made significant
contributions in either Ubuntu or big upstream projects (GNOME, KDE,
Mozilla, OpenOffice.org), or they have done smaller contributions but
have somebody who's done a lot vouch for them
  1a. If for the language there exist no translations in any of the big
projects (or rather, more importantly, KDE or GNOME, because they are
the basis for Ubuntu), you let anyone who shows interest run a team
  2. That person is subscribed to the main announcement mailing list
(whatever that is)
  3. That they have prepared at least a single wiki page with guidelines
on how to do translations for the particular language; it doesn't have
to be a wiki page, it can be a full web site containing detailed style
guide and instructions.

(I just thought of number 3, but I believe that it is essential,
especially since we'll be soon adding a link to such a web site for each
team)

> I assume that for some languages or people it will be easy to judge
> them as they are active and we can see their work on ubuntu or
> upstream projects.
> 
> For those we have no clue I was thinking of asking them that prior of
> establishing a Launchpad translation group they should join an
> upstream translation project and then asking the upstream translation
> project to give us a quote about his/her work. This is just an idea
> and I still don't think this is the right thing to do.

To keep things simple, just asking people proposing translation teams to
give us a few pointers should do the trick.  I.e. they can easily point
at PO files in both GNOME and KDE and we can check if they are listed as
either Last-Translator and/or in translator-credits/NAME OF TRANSLATORS.
We can probably figure out something similar for OOo and Mozilla, but
they should be able to tell us that themselves (i.e. where to look it
up).

Cheers,
Danilo