Live data from Hacker News

GitHub is now free for teams

github.blog

571–580 of 664 posts

Re: GitHub is now free for teams

#571

Hi HN, I'm the CEO of GitHub. Everyone at GitHub is really excited about this announcement, and I'm happy to answer any questions. We've wanted to make this change for the last 18 months, but needed our Enterprise business to be big enough to enable the free use of GitHub by the rest of the world. I'm happy to say that it's grown dramatically in the last year, and so we're able to make GitHub free for teams that don'…

> every developer on earth This now includes Iran, Syria, and Crimea. Bravo

No, It doesn't

Re: GitHub is now free for teams

#572
post #554

Hi HN, I'm the CEO of GitHub. Everyone at GitHub is really excited about this announcement, and I'm happy to answer any questions. We've wanted to make this change for the last 18 months, but needed our Enterprise business to be big enough to enable the free use of GitHub by the rest of the world. I'm happy to say that it's grown dramatically in the last year, and so we're able to make GitHub free for teams that don'…

Can you explain what happened to Atom development? I've seen numerous posts noting the sharp decline in contribution soon after the acquisition was announced. https://news.ycombinator.com/item?id=22601451 https://news.ycombinator.com/item?id=21142934 Without an official explanation, given the timing, it'd be reasonable to assume you pulled development resources away from it, the exact thing you actually went on Reddi…

You have the explanation laid out pretty well by chipotle_coyote in the comments of one of your linked posts.

https://news.ycombinator.com/item?id=22601557

Specifically:

> But the words of the linked Reddit comment from Nat Friedman were "we will continue to develop and support both Atom and VS Code going forward"; that's a true statement today. Atom is currently being developed and supported. That's a case of adhering to the letter of the statement rather than the spirit, I know. But that circles around to the problem of VSCode's rapid ascent in mindshare -- if your company ends up owning two very similar editors and they both have roughly equal downloads and community interest, you might try to support both equally. But if one of them has orders of magnitude more downloads and community interest than the other, you're going to focus your efforts on the popular one.

Re: GitHub is now free for teams

#573
post #17

Earlier quoted context omitted.

GitHub has significant vendor lock-in, so it makes sense to make it free to capture the market before a competitor gets traction. [Speculation:] Perhaps they've run the numbers and can figure out that they make enough money from enterprise clients and will make enough more money from the 'marketplace' being a channel for selling github integrations and addons to cover this cost of not trying to monetize through suppo…

What exactly is the lock-in mechanism? E.g. I have git repos where I use multiple remotes (1 Github, 2 Gitlab..). So git is the same as everwhere.. I never felt locked in. It's not too hard to transfer your repos to another provider.

GitHub is not git.

GitHub has pull requests, actions (mini CI integrations), other fuller integrations running off github hooks.

It's the issues, and pull requests that are the most immediate lock in. Transfer away and you lose your issues and PR history.

But more deeply it's the integrations. Even if it's all theoretically possible through other providers, if you have a working CI system set up to "just work" through GitHub then there's little chance you'll want to migrate to a different provider and have to re-do all that configuration.

Even with a dedicated dev-ops team it's weeks of disruption, not to mention the possibility to get half way through and discover something doesn't work the same way in [Competitor].

If you're up and running with github PRs driving JIRA issues and JIRA issues feeding into GitHub issues. And you have paid github marketplace integrations delivering value, then you're not going to look at a competitor unless that competitor is offering something that GitHub doesn't do.

Up to now the competitors have only differentiated on price as far as I can tell. There's certainly no killer feature of GitLab that people talk about.

Re: GitHub is now free for teams

#575

Earlier quoted context omitted.

I gave up on Atom this month because of the lack of development. Too bad really.

I gave up on Atom when it was released because it was the most slow editor I have ever seen. It single handy bias me against Electron app until I discover VSCode.

VSCode is electron-based.

Re: GitHub is now free for teams

#576

Earlier quoted context omitted.

I gave up on Atom when it was released because it was the most slow editor I have ever seen. It single handy bias me against Electron app until I discover VSCode.

VSCode is electron-based.

This is precisely what he is saying.

Re: GitHub is now free for teams

#577

Earlier quoted context omitted.

We're living with transparent juridical system and it works fine. Imagine that you could be thrown to jail without explaining a reason. That would be outrageous.

Are you willing to pay taxes for github usage!? You get what you pay for.

If it guaranteed that the repos stay up in perpetuity, that sounds amazing, actually.

Re: GitHub is now free for teams

#580
However, looks like the Actions minutes included in the Team plan have dropped from 10K to 3K, so if you're currently paying for a team plan and using Actions your costs might not decrease, or might increase a bit
Post reply on HN