[Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github (original) (raw)

Ben Finney ben+python at benfinney.id.au
Sun Nov 30 12🔞32 CET 2014

Donald Stufft <donald at stufft.io> writes:

I think there is a big difference here between using a closed source VCS or compiler and using a closed source code host. Namely in that the protocol is defined by git so switching from one host to another is easy.

GitHub deliberately encourages proprietary features that create valuable data that cannot be exported — the proprietary GitHub-specific pull requests being a prime example.

So it is only true to say one can export the data to a different host if one entirely abandons all those features which create GitHub-proprietary data.

If you want to re-write the PEP to be clear you are only talking about the repository hosting of GitHub, and not any of its extra features that make it so attractive to use their proprietary service, I'd be interested to see that.

On the other hand, if you want to promote those proprietary features as part of the PEP, then it is disingenuous to claim the data can be easily exported to a different host.

-- \ “Do not enter the lift backwards, and only when lit up.” | `\ —elevator, Leipzig | o_) | Ben Finney

More information about the Python-Dev mailing list