Live data from Hacker News

Golang Proposal: Just Use GitHub

github.com

1–10 of 86 posts

Re: Golang Proposal: Just Use GitHub

#2
I wonder if Google really loves Gerrit, or if it’s just a legacy NIH attachment and some of Google’s graybeards just refuse to let it go.

Having worked with Gerrit in the past, I can say without a shadow of a doubt, it’s an abomination and I’d lop off a limb rather than voluntarily use Gerrit again.

Re: Golang Proposal: Just Use GitHub

#3
The tyranny of GitHub. GitHub pull requests are one of the most cumbersome ways of contributing to OSS.

What people really like is:

a) The paper trail (I can show to my career manager that I've done some work).

b) The constant distractions that feel like work.

c) Minor issues seem like major contributions.

d) Self promotion.

Re: Golang Proposal: Just Use GitHub

#4
Kinda scary how de facto Github has become, that external tooling is discouraged. Github is a bad issue tracker, a bad code review tool, an ok wiki and a bad distribution platform. Still, one has to mostly use the whole package to get contributors.

(Github has other strengths, though)

Re: Golang Proposal: Just Use GitHub

#6
post #4

Kinda scary how de facto Github has become, that external tooling is discouraged. Github is a bad issue tracker, a bad code review tool, an ok wiki and a bad distribution platform. Still, one has to mostly use the whole package to get contributors. (Github has other strengths, though)

BitBucket is plenty popular as well, I run into projects that are on there instead of GH for Python. I kind of prefer BitBucket to GitHub the only thing GitHub does right is their "Explore" section which I don't think BitBucket has (or GitLab?) but that's about it for me. I don't care where one hosts code, as long as it's not some obscure server.

Re: Golang Proposal: Just Use GitHub

#9
In my experience, there are no debates so fraught and vicious as those over version control platforms.

Questions of more open governance for Go really ought to be separated from Github specifically. Moving from googlesource to Gitlab or Bitbucket would achieve the same thing. Which is actually not much: just because a project is on a given commercial hosting platform doesn't portend a change in how decisions get made over project direction, as many projects hosted on Github (and Gitlab and Bitbucket) illustrate.

Re: Golang Proposal: Just Use GitHub

#10
post #4

Kinda scary how de facto Github has become, that external tooling is discouraged. Github is a bad issue tracker, a bad code review tool, an ok wiki and a bad distribution platform. Still, one has to mostly use the whole package to get contributors. (Github has other strengths, though)

And it’s not even open source. They don’t follow the development model that so many of its users who are responsible for its success do.
Post reply on HN