Hi, Sorry should have taken time to look into this earlier. I'll have a look at the french translation tonight to see what was submitted.
Baptiste 2013/11/14 Kohsuke Kawaguchi <[email protected]> > > > Thank you for looking into this. A similar issue was reported in en_UK > locale, so it's clear that we have to revisit the process. > > I still don't have good sense on the scope of the problem. I wonder if I > should roll them back, or should try to just fix them one by one? > > > > On 11/12/2013 11:48 PM, Роман Каган wrote: > >> Hi, >> >> I've upgraded to 1.539 and discovered that russian localization is >> seriously spoiled. >> >> Some labels contain offensive words (!), some don't match the original, >> some are plain garbage. >> >> They were introduced by >> >> commit 7828dcb46d9a18f88cc8e71046edc9ee91ed95e6 >> Author: Kohsuke Kawaguchi <[email protected]> >> Date: Sun Oct 20 22:10:02 2013 -0700 >> >> Community-contributed localization for Russian (ru) >> >> >> So the problem is actually the quality of localization contributions >> submitted via the translation plugin (which comes bundled and enabled >> with the main jenkins package). >> >> AFAICS http://l10n.jenkins-ci.org/ accepts anonymous submissions so >> nothing prevents an irresponsible user from submitting whatever crap >> they like. >> > > We do capture the Jenkins instance ID that it came from, so once we know > the offender it is relatively easy to block it. > > > > What can be done about it? >> >> I guess the option of proofreading by a trusted editor before committing >> into the main tree may not be available for a number of languages. >> >> Perhaps forcing authentication (e.g. via github or jenkins' jira) in the >> translation plugin will make the contributions accountable and thus >> prevent junk submissions? >> > > This is a good idea. It's cheap enough to do and it makes people recognize > that we know who they are, and I think it'll act as a deterrence. > > Another idea that I had from the beginning, although it'll require more > effort, is to ask people to review other people's submissions in the same > UI. That is, when someone submits a translation in one language, we can ask > them to review a different submission from another person in the same > language and score them. In other words, we can also crowd-source reviewing. > > There's also a suggestion of placing a high bar on updating existing > translations as opposed to just adding it where it's missing. > > > > Thanks, >> Roman. >> >> P.S. I'll go through that commit and submit a patch fixing the obvious >> issues today or tomorrow. >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send >> an email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > -- > Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ > Try Jenkins Enterprise, our professional version of Jenkins > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
