[dragonsh]

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.

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's not wise to rely on goodwill of investors of github looking for profits. Also from ethical point of view it's really bad moving to a non community for profit infrastructure for a community driven project.

This is same mistake like moving from Python 2 to 3.

[iolothebard]

Try reading the article next time.

[dragonsh]

I read the article and the main reason for moving is wish of Guido and some developers personally. I was following the pep for Kallithea and hoped it will be picked up given Python is using mercurial which is already distributed and at par with git in features and workflow.

Also GitHub is another sourceforge, when Python did not move to sourceforge when 80-90% of developers were using it. I don't see why they want to move to GitHub just for source code management now when roundup will still be self hosted by Python. This is one of the reason I like gnu and gpl they not just build open source but continue to uphold the principals.

[warbiscuit]

Not just on par, for those of us who want reliable cross platform behavior and gui tools (TortoiseHg), git seems lacking compared to mercurial.

Github is pretty shiny and popular though :|

[tclancy]

>This is same mistake like moving from Python 2 to 3.

At least you're forward-thinking.