Live data from Hacker News

Introducing unlimited private repositories

github.com

311–320 of 662 posts

Re: Introducing unlimited private repositories

#311
post #229

Earlier quoted context omitted.

I personally like the bitbucket method. I get my private repos free, but I can only work with 5 people on them before I have to start paying.

It says you will be able to add a few collaborators. So I think it will be very similar in the end.

Except that you have to pay for GitHub.

Re: Introducing unlimited private repositories

#312

I find it quite hard to comprehend why people use Github for private repositories. There are many free alternatives. BitBucket seems to be the famous one, but Gitlab has grown into an amazing product with 3 different offerings; On premise community edition, on premise enterprise and hosted (like Github). We have used the on premise community edition for about 3 years now. I first installed it when you had to run abou…

If every organization went to free alternatives, not only would those free alternatives need a source of revenue to support the new business, I think you'd find they too will change their pricing structure to better fit the people that use their product.

One thing I also have to mention is a majority of for profit organizations have no problem paying for services they use. HN is a special snowflake on the internet, it's not a reliable source of market research by any means.

I can guarantee you none of the competitors are in it to provide a charity. They all want and NEED to make money somehow, I think you'll be surprised how long free solutions tend to last.

Re: Introducing unlimited private repositories

#313

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.

What about organizations that have many members, but few that actually contribute code? We have accounts for most of the people at our company so they can view issues and pull requests, but only about a dozen ever push code.

Re: Introducing unlimited private repositories

#314

Earlier quoted context omitted.

It's possible, but that's a weird requirement (weird you'd want all your clients on the same repo, anyway) and you'd be able to circumvent this and come out pretty swell on the other side if that money is really worth it to you.

Why would they not use the same repo? It can easily be a standard product - look at the example further downthread of the unreal engine: All clients get access to the code. 2 private repos and 90657 users. That's an extreme example, but we also have a single repo that a lot of collaborators get access to.

That's a good point. It still seems like an odd use-case!

Re: Introducing unlimited private repositories

#315
post #196

Nothing beats https://bitbucket.org/ when it comes to free, unlimited, private repositories. It has seen the first hosted repositories of far more startups than github ever will. Which is special achievement in itself.

Do you have numbers behind the first hosted repositories statement?

Re: Introducing unlimited private repositories

#316

Earlier quoted context omitted.

If you are non profit and open source do you really need private repos?

In a non-profit that I collaborate with [1] we use private repos to keep the server setup and some tickets that contain sensitive information (user data). All other code is open source. Obviously we don't want to keep api keys etc. in the public repos. [1] https://github.com/sozialhelden/wheelmap

You shouldn't be keeping api keys or other sensitive information in git at all. And please note -- if you do remove it from git, it will be available in your git history so that needs to be taken care of as well (should the repo ever become public -- a common "exploit").

Re: Introducing unlimited private repositories

#317
post #208

Earlier quoted context omitted.

For us as a small team it's a very positive change. Our monthly bill just went from $100 to $25.

And for us it's negative, our monthly bill has just increased by hundreds of dollars. In theory, our respective organisations could be in competition, and GitHub has just increased our monthly bill to subsidise your organisation, instead of shouldering the financial burden themselves.

The sheer irony of this statement is staggering. Github is a business and their goal is to make money. If you have 5x the number of people doing dev work on your code, then by definition you are a "larger" organization from their vantage point. Why wouldn't you pay more?

Re: Introducing unlimited private repositories

#318

I see absolutely no reason why one would pay GitHub for private repositories when there is Bitbucket, or much better alternative to GitHub altogether - GitLab.

Because businesses need money to survive and most have no problem spending it when it increases productivity or provides perceived value over another product.

Re: Introducing unlimited private repositories

#319
post #21

Pretty angry that Github have made this change with no mechanism for adding machine users without paying a per month charge. It seems like a key feature, which is currently horribly painful to manage and now expensive. How does everyone else create credentials that CI can use to checkout code?

Both Travis and Circle automatically install a deploy key into the project. It doesn't require additional machine users.

Semaphore works the same way.

Re: Introducing unlimited private repositories

#320
post #40

A small comparison: Team | Cost Before | Cost Now 1 repo, 5 users | $25 | $25 1 repo, 10 users | $25 | $70 11 repos, 5 users | $50 | $25 11 repos, 10 users | $50 | $70 5 repos, 50 users | $25 | $430 50 repos, 5 users | $100 | $25 50 repos, 50 users | $100 | $430 I'm not sure how common are organizations with few users and large number of repose - I guess software houses that keep old projects (for maintenance and fut…

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

It feels to me like there needs to be a distinction between users and developers now they've changed their pricing model, with developers getting full git access, and users getting read-only source viewing through a browser, issues, and wikis. That way agencies can add customers for collaboration without having thousands of users to pay for.
Post reply on HN