Live data from Hacker News

Python moves to GitHub

mail.python.org

11–20 of 119 posts

Re: Python moves to GitHub

#11
post #9
post #7

Earlier quoted context omitted.

The problem is with people's mindset that everything has to be on github. Large projects that dare to use self-hosted more fitting infrastructure like Phabricator tend to be punished socially.

I suspect what you're seeing as social punishment is people preferring the UX GitHub offers. That's just user choice in action

Not really, the inconvenience of having to register another account (which often means another set of password) is quite a big deal for entry.

Re: Python moves to GitHub

#12

Everyone is moving to GitHub these days. Why doesn't Gitlab.com get more love? Isn't their whole stack open source?

I will cut the BS and give you my thought: simply because few people are interested in maintaining GitLab. If I were in the dev's position, I would have more time to focus on improving build pipeline, like adding some cool bot.

Re: Python moves to GitHub

#13
post #11
post #9

Earlier quoted context omitted.

I suspect what you're seeing as social punishment is people preferring the UX GitHub offers. That's just user choice in action

Not really, the inconvenience of having to register another account (which often means another set of password) is quite a big deal for entry.

Usually you can log in with your github account.

Re: Python moves to GitHub

#14
post #11
post #9

Earlier quoted context omitted.

I suspect what you're seeing as social punishment is people preferring the UX GitHub offers. That's just user choice in action

Not really, the inconvenience of having to register another account (which often means another set of password) is quite a big deal for entry.

This. Github's UX is nice, but so is BitBucket's and other competitors'.

Re: Python moves to GitHub

#15
post #9
post #7

Earlier quoted context omitted.

The problem is with people's mindset that everything has to be on github. Large projects that dare to use self-hosted more fitting infrastructure like Phabricator tend to be punished socially.

I suspect what you're seeing as social punishment is people preferring the UX GitHub offers. That's just user choice in action

Maybe, and even despite the missing code review functionality, if you compare it to stuff like Phabricator.

Re: Python moves to GitHub

#16

GitHub's reign over public open source programming is a bit terrifying. But, it's been mostly benevolent so far, but I do find it troubling to trust a private company to keep dev's in mind, and not profit.

The good news is that it is straightforward to make a copy of much of the important public data on GH.

Even the issue tracking?

Re: Python moves to GitHub

#17
post #11
post #9

Earlier quoted context omitted.

I suspect what you're seeing as social punishment is people preferring the UX GitHub offers. That's just user choice in action

Not really, the inconvenience of having to register another account (which often means another set of password) is quite a big deal for entry.

I'd consider "single sign on that connects me to tons of projects' repos to be great UX. Personally, it (and the centralized API) are big reasons I use GitHub to interact with projects whenever possible

Re: Python moves to GitHub

#19
post #16

Earlier quoted context omitted.

The good news is that it is straightforward to make a copy of much of the important public data on GH.

Even the issue tracking?

Their API exposes issue data, and there are a handful of 3rd party API-based tools designed to back up / extract it.

Also, for anybody not already aware (I didn't know this for a long time): GitHub repo wikis are themselves git repos that use Gollum

Re: Python moves to GitHub

#20
post #16

Earlier quoted context omitted.

The good news is that it is straightforward to make a copy of much of the important public data on GH.

Even the issue tracking?

Someone will probably point out that data can be exported, but that is frankly irrelevant given that the URLs for your project are now embedded around the entire world to a domain name you don't control (github.com), and which your goal should be to "outlive". There is tons of historical content sitting on SourceForge and Google Code that has links all over the Internet pointed at, and it is a major issue that you can't migrate and take these links with you; if github.com offered "bring your own domain" as a feature for some moderate cost, it would be much more viable as a platform for people who care about the longevity of their projects.
Post reply on HN