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.
After listening to episode 321 of The Azure Podcast[0] my understanding was that Azure DevOps would eventually be phased out; question begins at ~10:30 and at about ~12:00 a rough timeline of 5 years was given with guidance to select GitHub if just starting out. 0: http://azpodcast.azurewebsites.net/post/Episode-321-GitHub
GitHub is now free for teams
491–500 of 664 posts
Re: GitHub is now free for teams
#492By and far the main difference between 'Team' ($4/person/month) and 'Enterprise' ($21/person/month) is SSO/LDAP [0]. The SSO tax is real [1]. [0]: https://github.com/pricing [1]: https://sso.tax/
Even setting that aside, SSO is a feature which is very meaningful to businesses and relatively meaningless to individuals. Because of that its often used to differentiate between the customers. This differentiation results in individuals getting a discount at the expense of the businesses; which to me makes sense.
Re: GitHub is now free for teams
#493Hi Nat, ICE kidnaps children and forces their captives to live in unsafe, inhumane, over-crowded conditions in the middle of a global pandemic. Why do you work with them?
Github donated the money ICE paid them to charities that are directly counteracting the bad things ICE is doing. Isn't that clearly better than just forcing ICE to install Gitlab?
Re: GitHub is now free for teams
#494Earlier quoted context omitted.
pretty off topic to bring up customers of a lightbulb factory to shame them for selling headlamps to tanks...
All right, point taken - this is a politically incorrect discussion and we should be self-censoring ourselves.
Re: GitHub is now free for teams
#495Seems like Github is feeling heat from GitLab/BitBucket. I guess the calculation here is that the enterprise contracts are where all the money is, and keeping smaller customers on GitHub is worth the price cut?
Re: GitHub is now free for teams
#496Earlier quoted context omitted.
You can buy extra build minutes. The missing 7k minutes would cost $56, which means teams with 12 or more devs who are using the full 10k minutes will be better off. Smaller teams using more than 10k will be worse off. It’s probably great news for the vast majority of teams.
This is only true if you're using exclusively Linux runners. If those same 7,000 minutes are on macOS, you're paying $560. On Windows, $112. At my company, we definitely use a mixture of all three for various things, so this will sting, with varying degrees, depending on how often we build new iOS, Mac, and Windows releases.
https://help.github.com/en/github/setting-up-and-managing-bi...
Re: GitHub is now free for teams
#497Earlier quoted context omitted.
All right, point taken - this is a politically incorrect discussion and we should be self-censoring ourselves.
No, your comment just doesn't make sense. Lightbulb manufacturers are not responsible for wars because tanks have lightbulbs in them, and GitHub is not responsible for all the harm in the world either because some bad actors use GitHub.
Re: GitHub is now free for teams
#498By and far the main difference between 'Team' ($4/person/month) and 'Enterprise' ($21/person/month) is SSO/LDAP [0]. The SSO tax is real [1]. [0]: https://github.com/pricing [1]: https://sso.tax/
Re: GitHub is now free for teams
#499Hi 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'd like to share feedback on GitHub Actions. Tried it out, and the learning curve was too much. I want to use stuff I already know -- e.g., write a Dockerfile, and then GH could run it on PR builds. The "workflow" concept didn't land for me, and I hope you consider a more generalized, open-source approach to running arbitrary scripts in response to PRs being opened, merges to master, etc.
The concept of actions is new, but it is brilliant compared to traditional approach of doing everything inside the CI jobs, or bring your own docker images.
Re: GitHub is now free for teams
#500Hi 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…