Live data from Hacker News

Go is moving to GitHub

groups.google.com

161–170 of 244 posts

Re: Go is moving to GitHub

#161

Earlier quoted context omitted.

> Still, both lack a lot of basic issue tracker and code > review features. I strongly disagree. What you might consider "basic features" I'd consider antifeatures. The bare simplicity of the issue tracker is precisely why I use it for my (large) projects. The PR model of code review scales elegantly to hundreds of contributors. I'd be devastated to see GitHub's collaboration tools move even a step toward the hellsca…

At least for code review, the problem isn't pull requests as-such. The features that drive me to use other tools (on top of guthub hosting, often) are things like: * The ability to mark which commits/files have been reviewed and so track progress. * The ability to distinguish resolved and unresolved issues * The ability to assign a reviewer based on which code is being altered in the PR. * Useful handling of history…

Beanstalk - private repo hosting for business - just released a brand new code review tool that we've been beta testing for a while now. It's rather nice and addresses many of the rough edges of pull requests. It's definitely for same-company teams as opposed to large open-source collaborative projects, though.

http://beanstalkapp.com

We host all of our private repos with Beanstalk, and use GH for our open source repos.

Re: Go is moving to GitHub

#162

Google Code has a really bad user interface. This migration makes sense. I wish they stuck with Mercurial and moved to Bitbucket instead, but Github is still better than Google Code.

Google Code needs web and UX designers STAT, or it will die.

Re: Go is moving to GitHub

#163
post #45

Google hosting Go on GitHub. Microsoft hosting .NET on GitHub. It must feel like an accomplishment to be implicitly endorsed by these companies. Considering open source's history, you'd think its primary management tool would be open source as well. I guess it's GitHub's combination of accessible design + performant version control + lack of ads + reliability that made it the premium source for anything open source.…

Am I the only one who thinks some more competition would be nice? I would like to see more code move into BitBucket or similar. New version of Kiln will make it possible to use Git and Mercurial against the same repository which sounds like a great feature (not sure if there is a free plan on Kiln yet).

Re: Go is moving to GitHub

#164
post #131

Earlier quoted context omitted.

We will use the GitHub issue tracker, which will allow easy cross references between go issues and other projects on github.

I have to agree that not using pull requests is missing out on the best feature of github. It's the social, low-overhead way to contribute to a repo. It seems like it must be possible to hook up a bot to github that watches for pull requests and submits them to gerrit... the Juju team has a bot that does that for our Reviewboard integration. It won't work for more complicated workflows that github doesn't support, li…

GitHub code review is terrible. I don't blame them for not using pull requests in the least. If not being able to pull is enough to stop people from contributing, how much is their contribution worth?

Re: Go is moving to GitHub

#165
post #45

Google hosting Go on GitHub. Microsoft hosting .NET on GitHub. It must feel like an accomplishment to be implicitly endorsed by these companies. Considering open source's history, you'd think its primary management tool would be open source as well. I guess it's GitHub's combination of accessible design + performant version control + lack of ads + reliability that made it the premium source for anything open source.…

Am I the only one who thinks some more competition would be nice? I would like to see more code move into BitBucket or similar. New version of Kiln will make it possible to use Git and Mercurial against the same repository which sounds like a great feature (not sure if there is a free plan on Kiln yet).

You are not the only one. We finally have decentralized tools only to... put all the eggs back into one basket!

Re: Go is moving to GitHub

#166
post #157

I guess its official, misogyny is ok in our industry. Have we forgotten about: http://lmgtfy.com/?q=github+misogyny ? I'm not sure github even experienced a dip in traffic. There are github alternatives, it took me 30 minutes to remove my github subscription and migrate my repos to bitbucket.

I will bite. How does using Github even remotely contribute to accepting misogyny in our industry?

I will bite back.

Github's corporate culture appears to be very anti-woman. There is plenty of available evidence to this effect. There is very little apparent diversity (of any sort) in their large team. https://github.com/about/team

Using Github contributes to the success of this monoculture and encourages tech leaders to revere and duplicate this model. It makes tech more difficult for people outside of that group - the white, straight, male group. It makes tech culture worse.

If I'm aware that you host on Github, I will make sure to consider what your competitors are doing before I use your service.

Re: Go is moving to GitHub

#167

Earlier quoted context omitted.

There are countless git frontends (easygit and git legit) that come to mind, and yet they all see negligible use. I think the cognitive load of using git is overrated. Yes, it could probably be simpler. No, you probably can't make simple and intuitive for everyone while retaining all the features. Given that it's also easy to work with e.g. subversion or mercurial and a git bridge, so you can use the client of your c…

The git CLI is a mess. It's inconsistent even within its own commands. For example, sometimes specifying remote and branch is done as "remote/branch" and sometimes as "remote branch". It even uses different words for the same thing - sometimes remove, sometimes rm sometimes -d. Common actions often require obscure command lines, like "make a new branch" which is git checkout -b instead of just "git branch". The reaso…

> For example, sometimes specifying remote and branch is done as "remote/branch" and sometimes as "remote branch".

AFAIK those usages are semantically different, and consistently so. For example, git pull actually is "repository ref" rather than "remote ref", and will go over the network to fetch the current status of ref from the given repository.

git merge, on the other hand, is simply "git merge ref"; when ref is of the form remote/branch, it will merge the current local state of remote/branch, which should be the state from the last git fetch. git merge does not access the network.

So: semantic differences, represented via different command line syntaxes. It's actually pretty reasonable, and it's pretty obvious if you've taken half an hour to understand the underlying data model of Git.

> Common actions often require obscure command lines, like "make a new branch" which is git checkout -b instead of just "git branch".

Actually, "git branch" is the command to create a new branch. "git checkout -b" is a shortcut for "create a new branch and move to that branch".

Re: Go is moving to GitHub

#168
I think these are two separate issues:

  1) Go is moving from Google Code to Github
  2) Go is moving from Mercurial to Git
To echo another user in the thread: "am I the only one who prefers Mercurial to Git?" In my view Mercurial is on par or even superior to Git, but lacks "Linus made it" fame. Too bad... I have used both Mercurial and Git and find hg command line interface much more intuitive to use. As for GUIs, there really isn't much difference between the two (too bad GitHub only supports git though).

Re: Go is moving to GitHub

#169
post #45

Google hosting Go on GitHub. Microsoft hosting .NET on GitHub. It must feel like an accomplishment to be implicitly endorsed by these companies. Considering open source's history, you'd think its primary management tool would be open source as well. I guess it's GitHub's combination of accessible design + performant version control + lack of ads + reliability that made it the premium source for anything open source.…

Am I the only one who thinks some more competition would be nice? I would like to see more code move into BitBucket or similar. New version of Kiln will make it possible to use Git and Mercurial against the same repository which sounds like a great feature (not sure if there is a free plan on Kiln yet).

Gitlab is gaining some traction, and should be considered indirect competition, and direct vs. github enterprise

Re: Go is moving to GitHub

#170
post #100

I think this is Google quietly admitting that Google Code is all but dead. They will not completely get rid of it, but I would not be surprised if they switch it to read only mode sometime soon. This is a momentous move for Github, especially with Microsoft moving .NET to Github as well. As someone who loves Github immensely, this makes me happy knowing that my favourite service is going to be around for a very long…

> I think this is Google quietly admitting that Google Code is all but dead. Well, I doubt that Google Code engineers or project managers had much, if anything, to do with the decision to move the Go project.

That they didn't have a say in this matter though, speaks volumes...
Post reply on HN