Sysadmin Load Reduction: Subversion Infrastructure

[Albert Astals Cid]

El diumenge, 10 de novembre de 2019, a les 3:04:03 CET, Alexander Potashev va escriure:
> вс, 10 нояб. 2019 г. в 04:10, Ben Cooksley <bcooksley at kde.org>:
> >
> > On Sun, Nov 10, 2019 at 11:19 AM Albert Astals Cid <aacid at kde.org> wrote:
> > >
> > > El dissabte, 9 de novembre de 2019, a les 21:22:16 CET, Ben Cooksley va escriure:
> > > > On Sun, Nov 10, 2019 at 8:37 AM Albert Astals Cid <aacid at kde.org> wrote:
> > > > >
> > > > > El dissabte, 9 de novembre de 2019, a les 19:27:07 CET, Ben Cooksley va escriure:
> > > > > > On Sun, Nov 10, 2019 at 7:18 AM Alexander Potashev <aspotashev at gmail.com> wrote:
> > > > > > >
> > > > > > > сб, 9 нояб. 2019 г. в 03:20, Ben Cooksley <bcooksley at kde.org>:
> > > > > > > > This would include the shutdown of WebSVN in particular, which when
> > > > > > > > coupled with the shutdown of our two CGit instances would also allow
> > > > > > > > for us to eliminate an entire virtual machine from our systems.
> > > > > > >
> > > > > > > Will there be any web interface for SVN after shutdown of WebSVN?
> > > > > > >
> > > > > > > Can we assume https://phabricator.kde.org/source/svn/ remains
> > > > > > > available during the next 10 years?
> > > > > > >
> > > > > >
> > > > > > Phabricator's browser will be retired as part of the shutdown of
> > > > > > Phabricator, which will take place once Gitlab has assumed
> > > > > > responsibility for code hosting and review, and the tasks have been
> > > > > > migrated from Phabricator.
> > > > > >
> > > > > > Should WebSVN be shutdown as well, then there would be no web
> > > > > > interface to our SVN repository.
> > > > >
> > > > > That's not acceptable.
> > > >
> > > > Mind explaining why?
> > >
> > > Because we use it in l10n.kde.org to link to po files.
> >
> > Mind detailing what those links are used for?
> 
> A common workflow suggested for translators without SVN account
> (and/or those who find it hard to use SVN) is as folllows:
> 
>  1. Go to https://l10n.kde.org/stats/gui/trunk-kf5/team/ru/ ("ru" for
> Russian) and pick a .po translation file that needs update - e.g.
> incomplete translation or one containing mistakes.
> 
>  2. Click on the .po file at l10n.kde.org to downloaded. WebSVN is
> used for this.
> 
>  3. Edit the downloaded .po file, send for review, etc.
> 
> 
> WebSVN is even mentioned in KDE's primary translation how-to:
> https://l10n.kde.org/docs/translation-howto/gui-translation.html

In addition to that we also use it in check-kde-tp-results to link to the particular version the check was run
e.g.
  https://l10n.kde.org/check-kde-tp-results/trunk-kf5/et/messages.html
links to 
  https://websvn.kde.org/trunk/l10n-kf5/et/messages/kdemultimedia/kwave.po?revision=1555006&view=markup
in case it was fixed later since the checks only run weekly.

Of course all all of this can be "fixed" by us providing having a "mirror of the l10n files" on l10n.kde.org but without having a clue on how websvn works it seems it'd be much easier to just keep running that instead of having to code our own mirror.

Cheers,
  Albert