Live data from Hacker News

GitHub is now free for teams

github.blog

301–310 of 664 posts

Re: GitHub is now free for teams

#301
post #51

Great news for everyone bar startups competing with them as it looks like Microsoft is turning their multi-billion acquisition of GitHub into a loss leader to get as many devs using their platform as possible, no doubt to flex seamless integrations into Azure which looks like they're executing exceptionally well with their acquisitions & new feature giveaways. From the side-lines it looks like they're slowly becoming…

So far Microsoft isn’t taking customers away from AWS. They’re just expanding the total market. But I do wonder if AWS will try to buy gitlab.

While Amazon tried to go into the private hosting and ci/cd market, they are not a dev tool company. Microsoft was born as one. When Amazon or Google would buy GitLab they would meaningless integrate it, reduce staff by half and then ruin it over time.

Maybe when Microsoft would have opened up some years earlier, Codeplex would not share the fate of Google Cloud.

Re: GitHub is now free for teams

#302

Earlier quoted context omitted.

SSO is a great benefit to the customers, with real tangible security and management benefits. I'm however speaking from the point of view of the service provider (the SaaS app) and about SAML in particular. I feel that the addition of SAML into a given service is a net-negative from that service's security point of view. It's a large additional complex attack surface, many open source SAML libraries that I've reviewe…

I'm a security researcher with a minor focus in SSO libraries, working on OIDC and SAML right now. I've discovered and reported some of the kinds of issues you're referring to. Both OIDC and SAML are fraught in implementation, but so are all login features. Meanwhile: we're discussing Github, not a random cat-sharing startup. Github has one of the larger security teams in the industry. The parties implicated in Githu…

100% agreed, GitHub SAML is unequivocally good. I'm in the "cat sharing startup", so my view and comments are colored by that perspective. Our options are to pay $$$ for a competent auth provider, or take on a much larger and complex security responsibility than it would seem at first, that might end up compromising our entire service.

I have a theory that one reason we don't see many your-SAML-implementation-is-completely-broken reports is precisely because it's a gated enterprise feature, so few independent security researchers have the access or ability to poke and prod at them outside of private penetration tests.

Re: GitHub is now free for teams

#303
post #297

Earlier quoted context omitted.

Both products have a bright future and millions of users, and so we're continuing to invest in both for the foreseeable future. We're also finding ways to improve integration between them, so people can use them together if they want to. GitHub Actions reuses a bunch of code from Pipelines under the hood, for example.

I get that you guys want to say that publicly, but let's be real. No company would invest a massive amount of money in a duplicate product. One product will eventually starve. I guess it is up to us to guess. Anyone? I see GitHub being the unmovable giant here. Microsoft is publicly developing on it, as opposed to Azure Dev Ops. It has a very large mind-share. More developers are willing to use it without having the…

> No company would invest a massive amount of money in a duplicate product.

I don't mean to be rude, but have you worked at a very large company like Microsoft or Amazon or Google? Redundant products are par for the course because of the byzantine internal politics and funding structures of big companies.

Re: GitHub is now free for teams

#304

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'…

I currently pay for a Github Silver plan annually ($600). When I try to downgrade to Free I get a message (in red) "You will no longer be able to access your private repositories or create new private repositories." How do I downgrade without losing all my private repos. Thank you!

Martin from GitHub here. Sorry about that message - team are rolling out an update to change the text and should be fixed soon. In the meantime if you ignore that message and downgrade from a legacy plan to Free then you will retain access to your private repositories.

Re: GitHub is now free for teams

#305
post #51

Great news for everyone bar startups competing with them as it looks like Microsoft is turning their multi-billion acquisition of GitHub into a loss leader to get as many devs using their platform as possible, no doubt to flex seamless integrations into Azure which looks like they're executing exceptionally well with their acquisitions & new feature giveaways. From the side-lines it looks like they're slowly becoming…

Blazor is slow to start but I think long-term will be a game changer.

As a .NET fanboy: no it will not be a game changer. It is too fat and does not fit the rest of the web development model. Similar to Xamarin it will be a platform to run C# and .NET on. It will not be the native or best experience. It will be productive and enable cross form factor reuse of code. Not more, not less.

Re: GitHub is now free for teams

#306

What safe guards are in place to prevent Microsoft from using GitHub to glean competitive intelligence? Just like Facebook used Onavo. https://www.wsj.com/articles/facebooks-onavo-gives-social-me...

The same safeguards that are in place on Azure (which is used by 99% of Fortune 500s for either Office 365 or cloud stuff), which is to say, ethics, and the fact that if they tried it once most of those companies would reduce their spend with Microsoft immediately. Not to mention the government contracts.

Re: GitHub is now free for teams

#307
post #282

Earlier quoted context omitted.

Good point. For anyone using the Student Developer Pack (or any other similar student offer), ask yourself this: Do you really want to become reliant on software and services that will cost you ~$70k/year as soon as you graduate? Well, unless they decide to switch market or shut down, in which case you're hosed no matter how much you're willing to pay.

And you only use a subset. And your employer is typically very happy to pay money for productivity. For sure this is to the benefit of the involved companies. But paying for good tooling is normal not strange. When you go to your local handyman he will tell you a lot about good and expensive tools.

> And your employer is typically very happy to pay money for productivity.

And that's money that's not going to better equipment. Or your salary. Or whatever else that it could be spent on that would have a far bigger effect.

> But paying for good tooling is normal not strange.

Paying for bad tooling is normal. Good tooling tends to come as a consequence of trying to solve something else.

Bad tooling also tends to be much more expensive to produce, because it's so prone to scope creep. Visual Studio had to build their own Docker wrapper, because telling people to just use it directly would give their users a glimpse of the outside world, and we can't have that!

> When you go to your local handyman he will tell you a lot about good and expensive tools.

The vital difference is that physical tools are expensive to duplicate and maintain. You can't distribute a hammer via BitTorrent.

Re: GitHub is now free for teams

#308

Earlier quoted context omitted.

> GitHub has significant vendor lock-in Do they? Unless you're on GitHub Enterprise, migrating is just moving your repos over the weekend, setting up new webhooks, emailing everyone a command to switch their upstream URL, and hoping the new workflow works for you. For teams of <100, this it one of the easier transitions to make.

How are you gonna migrate issues and actions?

Exaclty this. On gitlab you can run your CI runners on anything you like. Basically start docker and forget. Curious how github actions compare.

Update: apperantly github also has self hosted runners

https://help.github.com/en/actions/hosting-your-own-runners/...

Re: GitHub is now free for teams

#309

Earlier quoted context omitted.

I currently pay for a Github Silver plan annually ($600). When I try to downgrade to Free I get a message (in red) "You will no longer be able to access your private repositories or create new private repositories." How do I downgrade without losing all my private repos. Thank you!

Martin from GitHub here. Sorry about that message - team are rolling out an update to change the text and should be fixed soon. In the meantime if you ignore that message and downgrade from a legacy plan to Free then you will retain access to your private repositories.

thanks for the fast and reassuring answer, I appreciate it. I'll wait until that message goes away, I can't risk losing my private repos.

Re: GitHub is now free for teams

#310

Earlier quoted context omitted.

I'm a security researcher with a minor focus in SSO libraries, working on OIDC and SAML right now. I've discovered and reported some of the kinds of issues you're referring to. Both OIDC and SAML are fraught in implementation, but so are all login features. Meanwhile: we're discussing Github, not a random cat-sharing startup. Github has one of the larger security teams in the industry. The parties implicated in Githu…

100% agreed, GitHub SAML is unequivocally good. I'm in the "cat sharing startup", so my view and comments are colored by that perspective. Our options are to pay $$$ for a competent auth provider, or take on a much larger and complex security responsibility than it would seem at first, that might end up compromising our entire service. I have a theory that one reason we don't see many your-SAML-implementation-is-comp…

The riskiest components in SSO deployments are SP-side libraries, and those are all open source. If you want to use Okta to drive those libraries, the trial account you need is free.

The worst bugs here are indeed mostly private, but that's because they're feature bugs inside of people's random products; they're like every other bug in that regard. But people do find and report bugs in the SP libraries.

I agree that SAML is risky to implement; since we agree that Github SAML is an unalloyed good thing, we'd be searching for reasons to disagree at this point.

Post reply on HN