-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Feb 26, 2009, at 2:54 AM, Martin v. Löwis wrote:
Note that not switching from svn on the backend, but still allowing access with bzr, hg, and git is also an option. And there are two subcategories of that: we provide mirrors of svn branches in the
native format, and we do nothing, allowing the dvcs's use their svn- bridges to access the branches. Although I think in either case we could
provide hosting support for core committers.That's already the case, for bzr, right?
Correct, in that there are native bzr branches on code.python.org,
which I am currently trying to improve.
If we go this route though, then I think we should evaluate providing
the same level of support for other DVCSs people want. I'm not
volunteering to maintain the hg or git repos, but if volunteers came
forward, we should reorganize the url space and authentication stuff
so that they can easily be pulled from c.p.o.
Alternatively, we continue to provide the svn masters and let other
hosting facilities mirror the native branches (con: there will be a
delay) or let people use their <dvcs>-svn bridges, e.g. bzr-svn.
Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSaaYXnEjvBPtnXfVAQJ9ogP/atF6CV+OfjtgMoTd4fFYcu8yy2xTBxry 7W8uHbP93mMNHMy15R4sC16E7t/S7CX3IsA+DeTOPOUUb06ZGF9mcwo8FB2veUxB UP97TCMr+y7mNCgBLw+Ljjg4N6j9J1dlqGRbA7CekGD8DPIlXY8yYCuDAGM1YyQO r9kU2qiSuYw= =jh/i -----END PGP SIGNATURE-----