[Scilab-loc] Re: Settings for the scilab localization inLaunchPadTranslations

[Sylvestre Ledru]

Le vendredi 06 mai 2011 à 11:49 +0200, Kenneth Nielsen a écrit :
> 2011/5/6 Sylvestre Ledru <sylvestre.ledru at scilab.org>:
> > Le vendredi 06 mai 2011 à 11:01 +0200, Kenneth Nielsen a écrit :
> >> If Scilab decides
> >> to do it differently, then I wont loose any sleep over that. I'll just
> >> find another project that does care about quality. There are plenty of
> >> projects that are hungry for translator contributions.
> > We are interested by translator contributions... It is something I
> > cannot myself :)
> > I am trying to understand both points of view and to find a consensus.
> 
> Sure. I was just saying to underline that I am not some nut out on a
> crusade. It was not a threat, just a fact about how I work. I, like my
> team, and like many other have limited resources. I translate on a
> volunteer basis and I only have limited spare time. Therefore I can
> only contribute to a limited number projects and so I simply use these
> things as some of the criteria I use to select which one to contribute
> to.
Sure!
I am not arguing on it.

> >> > To be serious, if you do not want to loose half (at least) of Scilab
> >> > translators, please change the policy to "Structured"
> >>
> >> Structured wont make a difference in the case where
> >> launchpad-translators have inactive language teams. As I already
> >> explained, the difference between structures and restricted is what
> >> happens if there is no team for a language.
> >>
> >> > or "Open".  LP-translators cannot give nor quantity, neither quality of translations,
> >> > but the current translators can.
> >>
> >> I disagree but the is off course the choice if the Scilab teamm
> > I tend to agree that people more involved in teams will produce better translations before of their involvements.
> > However, AFAIK, launchpad restricted introduces to much "constraints"
> > for new comers.
> > Don't forget that most of Scilab users are not geeks but mathematicians
> > and physicists.
> 
> Well, since there is a Danish team in launchpad translators Structures
> or Restricted wont make a bit of difference for me. Lets just make
> sure we all understand what the difference is, see some of my other
> mails.
OK, Danish is OK but as far as I know, some lp teams are empty.

> >> > If you are still not sure, please create "Scilab translators" and approve
> >> > its members by yourself
> >>
> >> That is the next best solution. This will allow me the control I need
> >> in order for med to contribute.
> >
> > OK. I like this potential good solution. Any one has an objection for
> > this solution ?
> 
> Well as I wrote above, unnecessary bureaucracy is also one of the
> criteria that I use to select projects that I want to contribute to.
For now, it is what we have, you just need a lp account to contribute to
it.


> However, before you make such a change you should understand how it
> will work. The following will happen. Common for restricted and
> structured is that if you do assign a team or person within that group
> to the translations into a language, then it will be restricted to
> that team or person (so people casually dropping by cannot
> contribute). If you don't assign a person or team to the translation
> into a language, then the translation into that language will be open
> to all. If you make it a policy not assign anybody to the languages
> and use structured then the result is the same as open, and you might
> as well keep that.
OK, thanks for the explanations. 
So, a thing I could do could be to try to chat active people (or
identifying them). Chat with them if they agree to join/create a team. 
If they are OK, let's go for it. Otherwise, I don't not assign any team
and leave it like now.

How does it sound ?

Sylvestre