Golang Proposal: Just Use GitHub
github.com
Golang Proposal: Just Use GitHub
1–10 of 86 posts
Re: Golang Proposal: Just Use GitHub
#2Having 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
#3What 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(Github has other strengths, though)
Re: Golang Proposal: Just Use GitHub
#5Is a case in point of why github isn't the answer for everything.
Re: Golang Proposal: Just Use GitHub
#6Kinda 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
#7Re: Golang Proposal: Just Use GitHub
#8GitHub has ruined software development for adults.
Re: Golang Proposal: Just Use GitHub
#9Questions 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
#10Kinda 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)