For reference, KDE's annual voting on next year priorities is now open. If = you're interested in getting better online translations tools (while still = keeping the current existing SVN workflow for those who prefer offline) ple= ase consider voting for T11070 (original Phabricator link: https://phabrica= tor.kde.org/T11070). Vote invites were originally passed out "to the KDE community mailing list = [https://mail.kde.org/mailman/listinfo/kde-community] and everyone with a d= eveloper account". If you missed the invite and would like to get a vote, p= lease contact Lydia via their email (lydia@kde.org). Thanks, Scott =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Wednesday, July 17, 2019 12:46 AM, Luigi Toscano wrote: > Luigi Toscano ha scritto: > > > Scott ha scritto: > > > > > Hey All, > > > I realize I'm a new face, but I'm a big fan of KDE's experie= nce and in the > > > recent past on Twitter saw an effort to focus on a few core = projects to > > > improve the KDE ecosystem, etc. Making it easy to contribute= localization was > > > a particularly big pain point highlighted by several people = via multiple > > > duplicate items on Phabricator (https://phabricator.kde.org/= T11070). > > > The two primary points of concern by folk that I could disce= rn were: > > > > > > - From the Task: "don't break the existing workflow for te= ams who want to > > > translate directly from SVN" > > > o Weblate has SVN integration so it in theory would func= tion as a second > > > 'channel' by which localization is committed and not int= erfere with > > > folk's existing SVN workflows > > > > > > > That's not the only problem. For example, how does the tool handl= e the pending > > comments/reviews when some files are renamed or moved around? Wou= ld it need > > special handling? And so on. > > Also it should be possible to enable it by team and the committer= s can only be > > the people who have write access today to SVN (i.e. people with a= KDE > > developer account). > > This is the older thread where the discussion has been explored i= n a proper way: > > https://marc.info/?l=3Dkde-i18n-doc&m=3D143561152919896&w= =3D2 > > Also, it should support the summit branches for the teams who use summ= it, > instead of the normal translation branches. > > I personally think that there are few architectural changes that shoul= d be > done before switching in order to simplify the workflow (like making s= ure > that the usage of summit is automated for everyone and does not requir= e manual > intervention as it happens today). > > ----------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= -------------- > > Luigi