Live data from Hacker News

Introducing unlimited private repositories

github.com

91–100 of 662 posts

Re: Introducing unlimited private repositories

#91

What about companies like Epic Games that have few repos but many users? With their 2 private UnrealEngine and UnrealTournament repos they would have been paying $25 a month and under the new pricing structure will have to pay $815,913 per month... edit: That's based on what I can see as a UE4 subscriber, 2 private repos and 90657 users.

We are reaching out to customers that are in unique situations such as the one you're mentioning here. If you have questions about how the pricing changes affect you, please don’t hesitate to contact support@github.com.

So what you're saying is - you know your new pricing is even more ridiculous than your old pricing, but you're willing to burn a little profit to keep big-name clients for the sake of PR.

Gotcha.

Re: Introducing unlimited private repositories

#92
post #77

What about companies like Epic Games that have few repos but many users? With their 2 private UnrealEngine and UnrealTournament repos they would have been paying $25 a month and under the new pricing structure will have to pay $815,913 per month... edit: That's based on what I can see as a UE4 subscriber, 2 private repos and 90657 users.

Make "Epic Games" a personal account and add everyone as collabs and it's 7 bucks a month, down from 25?

The post says this about personal accounts: you can even invite a few collaborators. I can't find the exact definition of "a few", but I imagine it's less than 90657.

Re: Introducing unlimited private repositories

#93
Hopefully this opens the eyes of at least some people into realising that GitHib !== git, and GitHub !== dvcs (similarly, git !== dvcs). There are several alternatives out there, almost all of which provide more options at lower cost than GitHub.

I know, I know "everyone is familiar with github". If your developers can't function without GitHub specifically, you have a bigger problem than the new GitHub pricing.

Re: Introducing unlimited private repositories

#94

Earlier quoted context omitted.

Even for software houses, it's VERY problematic as we add customers to projects as external collaborators and we're going to get billed for that forever, even if most customers have very light usage, and even for non active projects. I was thrilled by this news but it's going to be completely unaffordable for us. We have 29 users and 51 external collaborators. We have recently upgraded to the Platinum plan ($2460/yr)…

I keep my eye on Microsoft's Visual Studio Team Services. It has a bit of a clunky name and aimed more at enterprises but I think at some point they will position it as a competitor to GitHub. It's free for the first five developers, and no charge for "stakeholder" user accounts. https://www.visualstudio.com/pricing/visual-studio-team-serv... So 29 users would be $182/m (check my maths) and you'd pay nothing for the…

Yes, your math is correct, verified with their pricing calculator https://azure.microsoft.com/en-us/pricing/calculator/?servic...

Thank you for posting this!

Re: Introducing unlimited private repositories

#95
post #70

This is way too expensive! Self-hosted GitLab is cheaper and has better uptime! Not to mention, they should have made you pay only for users with commit rights!

Only if you assign no value to your own time, and assume you can do a better job with availability and durability than a dedicated Operations team and a multi-million dollar budget.

Re: Introducing unlimited private repositories

#96

I'm sure a lot of people will be moving from Bitbucket to this, Bitbucket's plans were great for hundreds of repos, but Github's ecosystem is definitely preferable.

Why? BitBucket is superior in every respect, plus importantly they give free private repos for every user. No price gouging like we're seeing with GitHub.

Re: Introducing unlimited private repositories

#100

Its unfortunate that this doesn't promote trying to get business users to look at the code. In our organization 3 or 4 users are read only and really just go in at times to check specific errors, or logic for certain SQL queries, they don't really contribute. We will now have to pay $9 per month for these type of "read only" users.

Couldn't you just use the same account for all of them, with a shared password?

how would you restrict to repositories then? Given a large enough set of external stakeholders using a single account is not feasible.
Post reply on HN