Brief article on benchmarks of Python repository with leading DVCSen

[Barry Warsaw]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Feb 11, 2009, at 12:58 PM, Paul Moore wrote:

> OK, here's a question. Given the existence of the current "unofficial"
> DVCS branches, what benefits are there to non-core committers of the
> core moving to a DVCS?

Lots, many of which are outlined in PEP 374.

> My main concern, as a non-core developer, is that an official decision
> on a DVCS will to an extent result in the *other* DVCS branches dying
> off, or becoming unmaintained. So, as a non-core developer, I have to
> contend with the fact that a decision on a DVCS may exert pressure on
> me to move to using that DVCS, at least for Python work.

This will be the case for some segment of the Python development  
community, core or otherwise, regardless of what DVCS is chosen.  The  
only way to avoid this is to do nothing -- which is one of the options.

> If someone confirmed that regardless of which DVCS was chosen, a
> maintained, up to date Mercurial mirror of Python would be provided
> (and that patch submission processes would remain VCS-neutral) then
> I'd stop bothering.

To the extent that such mirrors can be run by people outside the small  
and overworked python.org admin team, I'm all for it.  Maybe this will  
motivate people to make Tailor rock and then provide that as a service  
to the Python community.  I seriously doubt the py.org admins will  
take any of that work on.  Dedicated, long-term volunteers are always  
welcome and might influence the decision to pull that service in-house.

Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iQCVAwUBSZQ+pHEjvBPtnXfVAQJ1eQP+OwJ16DGrmulArWFjzm+jZUmTnX3zndn5
4eOsjYPojDALdIBhq99KDzL2GE+HmPGx8/2uoCH2khwjAByiGOkttkydBtmSqbrM
owVmQSKfpAk3puezQrtcdHml7CkB5iJ80jvBzAovhlbnzt58tEntAHn3yEPiaReW
Eitwi4BaBlU=
=ubp5
-----END PGP SIGNATURE-----