The history behind the decision to move Python to GitHub

&gt; But to me, the development process is more important than worrying whether a cloud-based service publishes its source code<p>And that&#x27;s basically it (and I agree with him)<p>Do you have a problem with Github? All the information you need is in your clone of the Git repository.<p>(Ok, there are bug reports, wiki entries, but apparently those can be obtained using their API as well)

I feel whatever be the reason it was a wrong move to move Python to github which is new sourceforge just more shiny. I hope the Python community get together to support either kallithea or trac or gnu and move there.<p>In an open letter recently group of open source developers raised and highlighted pitfalls of using such closed source for profit infrastructure without community oversight. Also it shows the opaque nature of such services. It&#x27;s not wise to rely on goodwill of investors of github looking for profits. Also from ethical point of view it&#x27;s really bad moving to a non community for profit infrastructure for a community driven project.<p>This is same mistake like moving from Python 2 to 3.

&gt; there was no killer feature that GitLab had<p>This really is the crux of the argument and for the GitLab guys is really what they should think hard about.