Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub is now free for teams

github.blog

Post reply on HN
Print view View original

231–240 of 664 posts

Re: GitHub is now free for teams

#231

Post by tptacek »

Saaster wrote: post #174
cactus2093 wrote: post #147

Earlier quoted context omitted.

This doesn't make sense. Login of any kind can be a tricky problem, you need to handle passwords, rate limits, email verification, password resets, etc. In most popular web frameworks there are libraries you can drop-in that handle all of this for you (like Devise in rails). There are drop-in libraries like OmniAuth (again for ruby/rails) to make handling multiple types of Oauth login simple. The same could clearly b…

Passwords, rate limits, resets, etc. are the same for everyone, and so are the problems and the solutions to those. SAML on the other hand is different for each organization. Providers pay Auth0 and the like to have developers on staff who know the pitfalls and quirks of ADFS 3.0 on Windows Server 2012 R2, so they don't have to. Dealing with a single Okta as IdP integration is like the absolute best-case scenario the…

It's a little odd to say something is not a "net security benefit" and, in the next sentence, make a powerful case for it as a net security benefit. SSO is probably the most important organization security tool there is, and a survey of tech company CSOs will average it in the top 3, if not the top 2 technology acquisitions most would make at a new firm (this is a question I've actually surveyed).

Re: GitHub is now free for teams

#232

Post by lukevp »

GordonS wrote: post #182
natfriedman wrote: post #26

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

Hi Nat, with Microsoft now owning Github, I'm really curious to know what the future holds for both Azure DevOps and Github? I'm a user of both - Github for OSS, and Azure DevOps for private work. IMO, these areas are where they are best suited - pipelines in particular are really powerful in Azure DevOps, and user/permission management, AAD integration and integration with build agents are all excellent. I really li…

Same question here. We use the hosted version of Azure DevOps for work, but I use github for open source contributions. They both have their place, and DevOps feels more suited to enterprise use than GitHub right now.

Re: GitHub is now free for teams

#233

Post by jjeaff »

manigandham wrote: post #206
cjdu wrote: post #112

Earlier quoted context omitted.

Agreed. I cannot believe that GCP and AWS are so asleep at the wheel either. If I were them I would literally be throwing money at some of the GitHub folks to have them fix AWS or GCP. And it was should have been rather obvious when GitHub released the beta of Actions a few years ago. Actions remains the most important thing GitHub has done, ever, in my opinion. It might take a few more years for people to fully real…

There are dozens of CI/CD offerings and many are better designed than Github actions, including Gitlab's CI runners. I don't see what paying Github would do for AWS or GCP. They both have their own code repos, build pipelines, container registries, and more. Even Azure has its own DevOps product.

I use Gitlab's CI runners and I agree. However, I am pretty excited about the direction that Github is going with their actions. Having a directory of user created actions and integrations seems like gold to me and I hope Gitlab starts leaning that way soon.

Re: GitHub is now free for teams

#234

Post by diminish »

GordonS wrote: post #182
natfriedman wrote: post #26

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

Hi Nat, with Microsoft now owning Github, I'm really curious to know what the future holds for both Azure DevOps and Github? I'm a user of both - Github for OSS, and Azure DevOps for private work. IMO, these areas are where they are best suited - pipelines in particular are really powerful in Azure DevOps, and user/permission management, AAD integration and integration with build agents are all excellent. I really li…

Do you plan to make github enterprise available for free on their own premises for teams?

Re: GitHub is now free for teams

#235

Post by manigandham »

Someone1234 wrote: post #163
troughway wrote: post #142

Earlier quoted context omitted.

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

You mean Microsoft's latest attempt at Web Forms/Silverlight, a product that yet again tries to muddy the separation between client and server execution contexts using magic. Seems like every generation re-invents this idea, and every time it fails for the same fatal flaw: Illusions are just that, and you'll wind up hacking around the illusion if you want to do something not envisioned (or run into a bug in the secre…

There's nothing magic about it. Web Forms was a great innovation and brought the WinForms model to the web. It was more productive than anything else at the time and directly influenced MVC patterns (which asp.net itself went towards) and component-based UI.

Blazor is the next evolution in client-side and offers an alternative to building component UI with C# running through WebAssembly instead of Javascript. Again it's much more productive and lets backend teams reuse much of the same code, similar to JS/node projects today.

Blazor's server-side runtime is a optional model where all the component logic can run on the server and be delivered over a SignalR connection to further increase productivity and efficiency where it makes sense (highly constrained devices, local intranet apps, etc. There's even experimental projects to bring Blazor for mobile apps.

Re: GitHub is now free for teams

#236

Post by sitsye »

sytse wrote: post #197
Someone1234 wrote: post #129

I think GitHub are doing well, but one cannot deny that GitLab has carved out a fantastic niche (on-prem, private instances, OSS, etc) that GitHub doesn't compete in. So while I agree GitHub are "the" company to beat, I think GitLab is doing a good job of contrasting. PS - No affiliation with anyone.

Thanks for the kind words! For developers everywhere competition is great. We recently made 18 new features free and open source https://about.gitlab.com/blog/2020/03/30/new-features-to-cor... and today Github with an improved free plan and their team plan came down to the exact same price as our most affordable plan. BTW Maybe an idea to rename their lowest tier from team, may we suggest bronze? :) Since you mention…

Trying to be snide that GitHub should copy you is not a good look. I'm sure most people haven't forgotten that you built your entire business off their work. You used their open source git libraries without contributing back, you ripped off pull requests, and you copy-pasted their CSS for a long time.

Re: GitHub is now free for teams

#237

Post by tptacek »

closeparen wrote: post #168
Saaster wrote: post #88

Earlier quoted context omitted.

SAML (and 2FA to a lesser extent) comes with some serious support burdens on the companies offering it. There's a long tail of more or less broken SAML implementations on both the service and identity provider sides, provisioning issues, configuration issues, "Sally can't login on Tuesdays" issues, duplicated slightly-inconsistent data in IdP and Service side records issues... If you as a SaaS provider outsource your…

What about OpenID Connect? That seems a lot simpler, and also has open source implementations that aren't too intimidating.

It's not a technology problem. Integration with "foreign" SSOs is complicated no matter what protocol you use, with lots of corner cases and support costs, but these features are expensive for the same reason that single-day-turnaround short-notice flights between Chicago and NYC tend to be expensive: the people who want them have money to spend on them, and it isn't their money. That money pays for the cheap seats everyone else sits in.

Re: GitHub is now free for teams

#240

Post by RandallBrown »

closeparen wrote: post #181
dmw_ng wrote: post #63

This is an awesome change! In case anyone else was wondering, here's what you lose by cancelling: You are downgrading to GitHub Free After April 15, 2020, ... features and limits will change: Protected branches in private repos Draft PRs in private repos GitHub Pages in private repos (using 1) Wikis in private repos Code owners in private repos Multiple issue assignees in private repos Multiple PR assignees in privat…

It's not clear to me whether this is possible under any configuration, but: can you enforce a two-person rule? I'd like all users to be able to merge accepted PRs, but no one should be able to push directly to master (unless an admin specifically elevates permissions to do that). The only way I can think of is to have a bot be the only one with commit access, and to interact with the bot to do merging. But that seems…

This sounds like how my previous company had GitHub configured.

We couldn't push to master, but we could merge accepted PRs. Not sure if this was done with GitHub or with Git itself.

Post reply on HN