Last modified: 2012-03-26 23:34:19 UTC
It's possible to browse the source trees managed on gerrit.wikimedia.org. That is, if you know what you're doing. And you're patient enough to find it. And you have a good memory. And if you're logged in (since you can't seem to browse projects otherwise. Chad tells me that Ryan has ideas for fixing this up via redirect, so I'm capturing the request to set this up here and in RT: http://rt.wikimedia.org/Ticket/Display.html?id=2370
This was submitted in https://gerrit.wikimedia.org/r/#change,2611, but doesn't seem to be working properly. Raising priority a bit, this really needs to be in place sooner rather than later.
Roan and Timo are working on a new Gerrit interface improvement as visible in http://gerrit.pmtpa.wmflabs:8080/ (it doesn't have a public IP, you need to proxy to it to get there, see https://labsconsole.wikimedia.org/wiki/Help:Access#Accessing_web_services_using_a_SOCKS_proxy ) and that may fix this issue. Adding Roan to cc.
(In reply to comment #2) > Roan and Timo are working on a new Gerrit interface improvement as visible in > http://gerrit.pmtpa.wmflabs:8080/ (it doesn't have a public IP yet It does now: http://gerrit-dev.wmflabs.org/
This is still high priority, but is not a blocker for the Wednesday March 21st migration. Roan and Timo are still working on their new JS tweaks and haven't added the gitweb links yet, Ryan and Roan need to look at configuring Gerrit to work around the +2 thing, "but the style is something we can apply independently". They are planning to test it on a test Gerrit instance.
The gitweb redirects are in place now. So you can use something like https://gerrit.wikimedia.org/gitweb/mediawiki/core.git. Would still like a nice way to navigate the projects though.
(In reply to comment #5) > The gitweb redirects are in place now. So you can use something like > https://gerrit.wikimedia.org/gitweb/mediawiki/core.git. > This was the original intent of this bug, so I'm marking FIXED. > Would still like a nice way to navigate the projects though. And that is now bug 35510.
