Google haven't built up too much of a user base for GCP's Cloud Source Repositories service yet (my speculation), so I wonder if they're viewing Gitlab as an acquisition target. TBQH, I don't see Gitlab lasting too much longer without an acquisition event of some sort, when facing up against this sort of Microsoft-backed feature funding. And I say this as a bigger user of Gitlab than Github (primarily because of the…
GitHub is now free for teams
131–140 of 664 posts
Re: GitHub is now free for teams
#132Hi 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'…
That said, the news made me wonder what exactly I’m still paying for with my personal Pro account. I went to the pricing page https://github.com/pricing and it seems Pro isn’t even listed anymore? And the Billings page https://github.com/settings/billing says “Pages, Wikis, protected branches and more for Pro developers” without any further explanation or link to docs explaining the differences. I can only assume that Pro has the same set of features as the $4/user/mo Team plan, but the messaging is certainly pretty confusing, don’t you think?
(I sure hope this isn’t a sign of neglect for individual developers, who are still the backbone of open source activities.)
Re: GitHub is now free for teams
#133Earlier quoted context omitted.
This is a great change! One request: I wish that SAML was not an enterprise feature. SAML ought be a basic security feature like 2FA—it's especially valuable for open source teams who might use a mixture of services, and an easily accessible and cheap SSO solution would go a long way in raising the security bar for all teams, not just open source teams.
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…
Re: GitHub is now free for teams
#134Does “for teams” also apply to paid personal accounts?
Re: GitHub is now free for teams
#135Hi 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'…
Re: GitHub is now free for teams
#136Earlier quoted context omitted.
I feel like anyone who lived through the 90s could have expected "these kinds of results". Git is open source and widely supported, which doesn't benefit Microsoft. By causing GitHub-specific features to be an essential part of a "modern" or "industry standard" git workflow, they can capture more marketshare/attention, and cause alternatives to be sidelined. This requires removing all friction to entering the proprie…
Thank you, it summarises it pretty well. MS is back pretty strong. It's also to note they attacking on two fronts, the open source and startup folks (VS code, github, typescrip, azure) , and the enterprise with communication, productivity tools and cloud infra (Teams, Office 365, Azure) Owned.
Re: GitHub is now free for teams
#137Earlier quoted context omitted.
Personally, I have been favoring Gitlab over Github because Gitlab allows private repos on the free tier.
I have been favoring Gitlab over Github because their CI is the best CI I've ever used. It just works, whereas every other CI found a way to make things hard for me. You can even spin up postgres and redis instances for tests by just specifying that you want them. It's amazing.
Re: GitHub is now free for teams
#138Earlier 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…
What is Actions?
Re: GitHub is now free for teams
#139This 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…
Re: GitHub is now free for teams
#140Hi 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'…
Hey Nat glad to see you here. A few days ago one of the biggest team collaborative games (Space Station 13) got banned on GitHub without a public explanation from GitHub staff, but some suspect it was because the code contained bad words and slurs. Do you know if this is why the project was banned, and will these new private team repos be subject to the same terms/rules?
I worry about the community dying and losing my favorite game, but have taken solace in the fact that the source will always be publicly available. If it was banned from GitHub, that's a major problem.