[trac] add mirror/backup repository for trac plugins

[philll]

Background

We currently use a vast amount of trac plugins, mostly provided by trac-hacks.org Apparently, that website and its repositories respectively do not have a very good uptime and are sometimes unavailable for quite some time (several weeks last time), which prohibits deploying test or live instances of our Trac instance in the infrastructure.

What to change

Provide a backup mirror repository with all our Trac plugins used to ensure they are available in case of a downtime of our plugin providers.

[matze]

Since GitHub supports Subversion for quite a while now¹, and because all plug-ins from trac-hacks.org are fetched via SVN over HTTP², and because we already maintain an adblockplus organization at GitHub³, I like to recommend forking the plug-ins in use into GitHub repositories, in order to avoid maintenance overhead.

This, however, needs to be done by someone who actually has owner permissions there, and can import the following resources:

• svn+http://trac-hacks.org/svn/blackmagictickettweaksplugin/0.12
• svn+http://trac-hacks.org/svn/sensitiveticketsplugin/trunk
• svn+http://trac-hacks.org/svn/accountmanagerplugin/tags/acct_mgr-0.4.4
• svn+http://trac-hacks.org/svn/tractickettemplateplugin/0.11
• svn+http://trac-hacks.org/svn/autocompleteusersplugin/trunk
• svn+http://trac-hacks.org/svn/masterticketsplugin/trunk
• svn+http://trac-hacks.org/svn/nevernotifyupdaterplugin/1.0
• svn+http://trac-hacks.org/svn/tagsplugin/tags/0.7

Afterwards I can update the puppet files.

[¹] ​https://github.com/blog/626-announcing-svn-support
[²] ​https://hg.adblockplus.org/infrastructure/file/cd938dae966c/modules/trac/manifests/init.pp#l61
[³] ​https://github.com/adblockplus

[philll]

@trev: Your opinion on matze's suggestion?

[trev]

GitHub is still a third-party website, the idea is to have these repositories on ​hg.adblockplus.org. Import from SVN is pretty easy ​using the Convert extension.

[matze]

Well, the ticket description only states uptime and similar issues in the background description. I hardly doubt that GitHub's availability (​https://status.github.com/) would become an issue for us. (In contrast; we do not care about our own availability that much right now..) Furthermore, the effort required to use this option is almost node.

Although we can use Mercurial and our own server to host the mirror repos as well, the import and future updates are a bit more time consuming.

However, in fact is does not really matter where the mirrors are, as long as they're reliable.

@trev: It's up to you anyway. Please either import the modules to hg.adblockplus.org or github.com (AFAIK we can't do that due to the lack of permissions in either case). thx

[matze]

Speaking of availability: #167 ... ;-D

[trev]

We should really have all dependencies on our infrastructure - then we only need to care about availability of our own infrastructure. Plus: we cannot have repositories on GitHub as subrepositories. Plus: our scripts don't need to consider multiple possible sources (and formats). Updating really isn't the issue.

[matze]

Agreed. Still, I cannot import new repositories. In case you won't find the time; whom else can I address regarding this task?

[matze]

This one's obsolete by now.