Sysadmin Load Reduction: Subversion Infrastructure

[Ben Cooksley]

Hi all,

This has been quite the long thread for one that was started only
around 2 days ago, so thought I would summarise things:

On the topic of removal of the Subversion mirrors, there have been no
objections, so we will proceed with this.

With regards to removal of access for everyone but translators, there
have been two objections noted to this. One concerned compliance with
the Manifesto, whilst the other was concerned with creating obstacles.
Given that restricting access to the websites is still compliant with
the Manifesto despite the lack of a clear clause permitting this I
don't believe that not granting access by default to Subversion should
be an issue, so would like to proceed with this as well.

That leaves the last point, which has generated the most contention,
the removal of WebSVN (websvn.kde.org).

Based on the responses, it would appear that translation workflows are
currently heavily embedded with and tightly dependent on this service.
This would indicate that we would need to keep this service around for
now.

With just a few websites left on Subversion though, I would like to
know if the translation teams have a plan for how they will continue
to do things in the long term, and whether this includes a migration
away from Subversion (as otherwise we are maintaining indefinitely a
Subversion repository, customised hooks, mirroring infrastructure,
WebSVN, and support for the email notifications from those customised
hooks within other systems such as our IRC Bots and Bugzilla)

Regards,
Ben