[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Having the merge/scatter script on a kde server for French locale
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2019-06-10 16:20:41
Message-ID: 1567469.aaL5ijfqsS () xps
[Download RAW message or body]

El dilluns, 10 de juny de 2019, a les 12:52:00 CEST, Johnny Jazeix va escriure:
> Hi,
> 
> Le ven. 7 juin 2019 à 00:34, Albert Astals Cid <aacid@kde.org> a écrit :
> > 
> > El dimarts, 28 de maig de 2019, a les 11:35:58 CEST, Johnny Jazeix va escriure:
> > > Hi,
> > > 
> > > is there still any blocking point to have it on the server or points
> > > to discuss? Else, I'll fill a ticket for sysadmin next week.
> > 
> > What is missing from my side is "a plan".
> > 
> > Who makes sure things aren't broken?
> > Who fixes it when it breaks? (and it will, someone will update python to use a \
> > feature not available on the serve or whatever)
> 
> Well, it's the same situation as now. If it breaks now and nobody is
> able to fix it, whether it runs on a local server or on a kde one will
> be the same.

No, it is not the same. If you're doing things that break randomly for you, it's your \
problem.

If in KDE we're providing a service N people are using and it breaks, it's a problem \
for N people and it has to be fixed.

> Can't we consider the tool mature? There isn't a lot of changes in it,
> so not a lot of risks something breaks:
> > svn log trunk/l10n-support/pology/scripts/ | grep ^r
> r1523767 | sdepiets | 2018-08-30 12:16:40 +0200 (Thu, 30 Aug 2018) | 1 line
> r1515443 | ilic | 2018-05-11 09:33:49 +0200 (Fri, 11 May 2018) | 2 lines
> r1466801 | adrianchavesfernandez | 2016-08-10 18:26:56 +0200 (Wed, 10
> Aug 2016) | 1 line
> r1447852 | ilic | 2015-12-21 15:06:01 +0100 (Mon, 21 Dec 2015) | 6 lines

It's not the tool itself that is problematic. It's the maintaince of all the things \
around the tool. Does it need a new python? Does it need a bugfix because something \
else happened?

You'd be surprised the amount of work Luigi, me  and others put on making sure the \
whole scripty thing runs smoothly. (As a data point i've made 182 commits since \
january on l10n-related stuff, and i am not a translator anymore, that means almost \
one commit a day just to try to make things be as good as they are)

We need someone that knows what he's doing that makes the same commitment for this.

Cheers,
  Albert

> 
> Johnny
> 
> > 
> > Cheers,
> > Albert
> > 
> > 
> > > 
> > > Johnny
> > > 
> 


[prev in list] [next in list] [prev in thread] [next in thread]