User:😂/Gerrit repo browsing

We need to look at how we're currently doing repository browsing.

Right now
Currently, we use Gitweb proxied through Gerrit. There's a couple of benefits to this: However, it's got some major drawbacks:
 * Gerrit handles most of it automatically, including auth
 * We just use the native gitweb package from Ubuntu
 * Load on gitweb increases load on the box we're running Gerrit on.
 * Gitweb sucks (it's slow, doesn't cache well, and has an awful UI)

Proposed idea

 * Replicate git repos to git.wikimedia.org (location tbd), minus the one private repo & draft changes
 * Should be able to do this with existing ACL options.
 * Setup the git viewer of choice
 * cgit -- really really fast. UI's about the same as gitweb though :\
 * gitblit -- if it's not the plugin, we can cache more agressively and dedicate resources to it, rather than being in the same resource pool as gerrit
 * gitiles -- developed by Gerrit team, clean UI. Possibly lacking a few features.
 * Configure gerrit to point to this new service instead of the proxied gitweb

Known concerns

 * We won't be able to view draft changes from the git viewer.
 * This is probably ok, actually.
 * Will need a config option to gerrit to disable the link to avoid confusion?
 * Won't we lose authentication provided by Gerrit?
 * Yes, but since all of our repositories are viewable to anons (minus one), we don't really need this.
 * Won't existing gitweb urls break?
 * Yes. We could possibly set up some rudimentary redirection, but it wouldn't be worth it to catch all possible edge cases (nor would they cleanly map 1:1)

Cool extra things we could maybe do as a result

 * We could allow cloning over http(s) from git.wikimedia.org, providing a faster mirror for people who don't intend to push to gerrit
 * Since it's all public data and auth isn't a concern, we could even possibly support the even-faster git:// daemon.