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

List:       kde-i18n-doc
Subject:    Re: With GitLab adoption, does this mean the end of SVN, and start of Git workflow?
From:       Luigi Toscano <luigi.toscano () tiscali ! it>
Date:       2019-10-01 8:27:26
Message-ID: 2d3005ea-b64d-3e55-5aa7-307d0e1cde1b () tiscali ! it
[Download RAW message or body]

Guo Yunhe ha scritto:
> We, Simplified Chinese team, have been running Crowdin + SVN for two years. Users \
> can either commit to SVN or Crowdin as long as they are not translating the same \
> string. We didn't change anything or add any restriction to SVN. Our scripts are \
> here https://github.com/KDE-China/crowdin <https://github.com/KDE-China/crowdin> 
> Here is also a thread on Phabricator https://phabricator.kde.org/T11070 \
> <https://phabricator.kde.org/T11070> 
> As you can see, a lot of contributors want to create an online translation system. \
> But here is no clear "go ahead" and required server resources from KDE. 

You mentioned resource needed many times, but this is *not* a problem with the
resources.
As I tried to say many times, we need to untangle and simplify some of the
workflow, reducing the number of operations that needs to be done on the svn
side (renames and moves), and reducing the number of branches that people
should care of (by making sure that posummit is implemented for everyone and
automated). Only after this we can add another piece on top of the mechanism.

So please please don't ask about "required server resources". That's not the
problem.

We discussed about the todo during the last Akademy. Unfortunately the
notes.kde.org service has been discontinued, so the notes can be only accessed
in a bit hacking way right now by downloading this file:

https://share.kde.org/remote.php/webdav/Community Notes/akademy2019-bof-i18n.html

-- 
Luigi


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