Live data from Hacker News

Introducing unlimited private repositories

github.com

321–330 of 662 posts

Re: Introducing unlimited private repositories

#321

Have been using Github for a community radio station, have been encouraging all staffers to use github accounts to file issues against our private repos, etc. The friendly policies for many collaborators have made this attractive, even though most users have rarely interacted with the repos, if at all. Now each user for the private repo has a significant cost (pretty significant for a non-profit community radio stati…

Did you evaluate Discourse for your use case? You can self host it cheaply on a small vps, and it's great for non dev issues discussion.

Re: Introducing unlimited private repositories

#322

1. Take a gazillion dollars in funding on an over-hyped valuation, 2. Go through significant organizational changes that end up with the departure of a co-founder (and more suits in the building). 3. Notice that a significant segment of your growth (VC-funded startups) are running out of money. 4. Switch to a user-based pricing to generate more revenue for investors, but spin it as a freebie "Hey! Look at the cool un…

Points 1-2 seem irrelevant to your argument.

> 4. Switch to a user-based pricing to generate more revenue for investors

You add "for investors" as a slur, like it's a bad thing. Every company, public or private, has investors -- even if it's just the founders.

> but spin it as a freebie "Hey! Look at the cool unlimited shit! No, no! Don't pay attention to the fact you're gonna be charged 3 times as much as before for the same service".

Except not everyone will be charged 3x as much. Many will be charged much less. It totally depends on the setup.

I have heard countless times over the years what a pain it is for orgs to be charged per repo. It incentives monolithic repos.

Equally important: from the perspective of a company trying to maintain budgets, it might actually make more sense to _them_. Factoring Github as a per-head charge, similar to everything from Slack/Gmail/Photoshop to laptops to food and other perks to healthcare benefits, might make things easier than worrying about whether your employees are structuring their repos in a way that minimizes costs.

Re: Introducing unlimited private repositories

#323
post #76

Earlier quoted context omitted.

>I guess software houses that keep old projects (for maintenance and future requests from clients) fall into this category, but who else? Companies using micro services? Companies that don't want to have one big repository for their software?

Good point. Also, before having 1 repository was a way to avoid higher bill. Now it'd require to have just 1 user which I doubt anyone will try to do.

Then again with git this isn't so much of a problem, if you aren't wanting to play the blame game this works quite well.

Re: Introducing unlimited private repositories

#324

As a solo developer who had currently paid up for monthly access annually, I feel obligated to feed back that this is pretty good news for me. Go github. The 5 private repositories was a bit grating and making me considering a move elsewhere. I was going to have to consider changing how I stored/structured my projects in order to stay under what seemed to me to a relatively arbitrary limit, which interfered with some…

Five private repos were more then enough for me.

When I ran out of them, I noticed that there's at least one that either does not need to be private anymore or just does not have to be on GitHub since I ditched that idea. It was a nice way for me to keep my GitHub profile nice and tidy.

Re: Introducing unlimited private repositories

#325
This change was beneficial to me.

Before upgrading, a grand total of 4 users had access to our private repositories, of which we were only using 7 out of 10. I was nervous about running out of repositories moreso than the cost of adding people.

(If we grow our team, it's because we have a lot of client work that's outside my immediate strong suits and we had to hire. If we do that twice, I'll gladly pay the extra $9/month.)

Re: Introducing unlimited private repositories

#326

1. Take a gazillion dollars in funding on an over-hyped valuation, 2. Go through significant organizational changes that end up with the departure of a co-founder (and more suits in the building). 3. Notice that a significant segment of your growth (VC-funded startups) are running out of money. 4. Switch to a user-based pricing to generate more revenue for investors, but spin it as a freebie "Hey! Look at the cool un…

From the perspective of a customer: repositories should be cheap, users shouldn't be. This is a positive change and one that will make me strongly consider moving from BitBucket to GitHub.

I've worked at places with two developers and 150 repositories. I've worked at places with 12 developers and 5 repositories. Who do you think gets more marginal utility out of another repository?

Every place I've worked that hasn't used GitHub either did so because of a regulatory reason (HIPAA and not wanting to do on-premise) or because the per-repository pricing model made it absolutely stupid expensive, or dumped you straight into Enterprise.

If you make a lot of money off a single private repo with many users, you'll move from "so cheap you don't even need to think about it" to "market rate." If you make a little money off of a lot of repos with a handful of users, you'll move from "don't even consider it due to cost" to "let's try it out for six months and see how it goes."

Re: Introducing unlimited private repositories

#327
post #247

I find it interesting that so many people here are unhappy with the change. Sure, prices will go up for a lot of organizations, but is $9/worker/month really a lot to pay for all the stuff GitHub offers? At Bay Area prices isn't that about 5 minutes of developer pay per month? For independent use it seems like a very positive change, in fact I'm guessing it's a direct challenge to GitLab. I was considering moving my…

> At Bay Area prices isn't that about 5 minutes of developer pay per month?

I work for an academic nonprofit. Asking to spend any money is like pulling teeth, and any purchase I make has to go through many layers of bureaucracy who don't understand or care what I do and have no incentive to make my life easier. I don't want to leave Github, but now I have to, because I just won't get the approval to spend hundreds a year. But I know that's nothing to Bay Area companies, so the rest of us will just go kick rocks or something.

Re: Introducing unlimited private repositories

#328

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

Fix your security.

Re: Introducing unlimited private repositories

#329

Earlier quoted context omitted.

Majority user, here. I already pay GitHub monthly because I have some repos that I want private. I'm a solo dev, only hacking on side projects that may or may not be something one day, but want to keep them private anyway. My bill is about to go down, and my benefits go up. All in all, I'm quite alright with this change, agree that it's positive. I get that it gets worse if I ever take on N number of developers, but…

I'm curious, as a solo dev, had you considered bitbicket?

I've used BitBucket as a solo dev working on personal projects, a solo consultant, and an employee on a team. It's pretty mediocre, especially if you look beyond its integration with the rest of the Atlassian ecosystem.

The number of times I've wanted to search a repo for something only to have to clone it and search in my IDE is staggering.

Re: Introducing unlimited private repositories

#330
This is awesome! I have wanted a different pricing structure for personal accounts for a long time.

And for those who have issues with the organizational changes, did you see?

> I am an existing organization customer and prefer the per-repository plans. Can I remain on my current plan?

> Yes, you can choose to continue paying based on the number of repositories you use. You can also upgrade or downgrade in the legacy repository structure based on the number of repositories you need.

Post reply on HN