using transparent gateways to the launchpad platform?

[Denys Duchier]

John Arbash Meinel <john at arbash-meinel.com> writes:

> If I understand correctly, you're saying that the machines are behind a
> firewall which refuses to route from their machine to
> bazaar.launchpad.net, correct?

Not exactly.  I am saying that they are using machines on a local subnet
for which NO NAT translation is provided AT ALL: they can only access
outside services through gateways.

> For starters, I'm pretty sure there is only bazaar.launchpad.net (I
> don't think they need to use bazaar.staging.launchpad.net, etc.) Do they
> have HTTP access?

they have http access (through a gateway).  however, if they choose to
develop a project using launchpad, they also need access to
code.launchpad.net, I think, in order to push branches.

I want them to have the usual access to all launchpad facilities through
the documented URLs.

In previous years, most of them chose to use svn simply because it was
easy to setup a project (e.g. on sourceforge) which could be accessed
through http both from within and from without the university.

It is a sad state of affairs when I have difficulties promoting a better
alternative simply because hosting solutions are not compatible with the
prevalent security restrictions enforced in our academic environments.

I am thinking of trying to write a "rerouter" plugin that would provide
alternative routing of URLs (basically mapping triples (proto, host,
port) to other such triples).  It would register new (alternative)
transports for certain protos.  I have never looked too deeply into this
part of the code base, so my ideas are a little hazy.  Help is welcome.

Cheers,

--Denys