Sysadmin Load Reduction: Subversion Infrastructure

Friedrich W. H. Kossebau kossebau at kde.org
Sat Nov 9 22:47:26 GMT 2019


Am Samstag, 9. November 2019, 21:22:16 CET schrieb Ben Cooksley:
> 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?

FWIW, everytime I had to deal with translations as developer (like checking 
pot files as well as .po files contents) I found having the web interface and 
its browsing feature very valuable to quickly find what I was looking for, 
over having to locally mess around with svn commands and juggling between 
commandline & file viewers. Including url bookmarks for quick access to 
browsing certain sets of files.

Incidents which I remember right now included:
* finding out whether extraction scripts were working as intended
* comparing translations seen by users over what they should see

Are there any other KDE clients of the svn repos still around, besides 
translation system?
Perhaps the "full clone" needed for WebSVN could be reduced to the translation 
subtrees, would that improve situation to a degree if possible? (well, you 
surely thought of this yourself, just in case)

For me as developer contributor to projects in KDE spheres, losing the web 
browsing interface for raw translation files would be a regression in 
developer experience.

Cheers
Friedrich




More information about the kde-community mailing list