Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing unlimited private repositories

github.com

Post reply on HN
Print view View original

541–550 of 662 posts

Re: Introducing unlimited private repositories

#541

Post by piotrkubisa »

LeifCarrotson wrote: post #246
tmaly wrote: 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.

Agreed. The goal should be accurate market segmentation. Students, open-source devs, and hobbyists pay little or nothing, small shops pay some, and large enterprises pay more. Collaborator count seems to do that better than most metrics.

It is worth noting that GitHub organizes the Student Developer Pack[1] which comes with a Micro plan ($7 - max 5 repos). It means GitHub will offer unlimited public and private repos for 2-3 years for students who were selected.

[1]: https://education.github.com/pack

Re: Introducing unlimited private repositories

#542

Post by teraflop »

lox wrote: post #108
giovannibajo1 wrote: post #30

Earlier quoted context omitted.

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

That's fine if you have a single repo, but CI normally needs to access lots of different repos. GitHub's documentation describes why you need machine users for anything but the most trivial deployment. https://developer.github.com/guides/managing-deploy-keys/ It's also what GitHub does internally.

If I understand that page correctly, the only real difference is that Github arbitrarily prevents you from using the same deploy key for multiple repositories. If they lifted that restriction, this problem would go away.

Re: Introducing unlimited private repositories

#543

Post by Alupis »

cstejerean wrote: post #171
hunvreus wrote: post #130

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…

Per user pricing makes a lot more sense than per repo pricing. This way larger organizations pay more money than smaller ones regardless of how they structure their code. This is a good deal for small organizations that like to have many small repositories (for internal libraries, utilities, micro services, modules, etc). Sure, it screws up a few models that rely on external collaborators to get access to private rep…

My company, for one, was actually in the middle of shifting to BitBucket off of Github, because the costs were becoming unjustifiable.

We have a growing number of repos that are more-or-less "finished" projects, and few if any changes are made per year. Accounting was starting to groan... and BitBucket's model fit our small team almost perfectly, although Github's UI, flow, etc, was, in our opinion, still better. New talent almost always has an existing Github account we can integrate, instead of needing to make and manage a new BitBucket account.

Now, with this news, we'll just reverse course and stick it out with Github.

Re: Introducing unlimited private repositories

#544

Post by TrevorJ »

sequoia wrote: post #508
fps wrote: post #269

Earlier quoted context omitted.

I work for a non-profit open source organization that collaborates on github ( https://github.com/edx/ ) We have lots of people who aren't employees, but have signed a contributor agreement with our organization and contribute changes to our software. Our bill will go up from $200/month to over $2000/month with this new pricing. We can afford it (it's still a small fraction of our AWS bill) but it will force us to lo…

> We have lots of people who aren't employees, but have signed a contributor agreement with our organization and contribute changes to our software. So you have volunteers, working on your proprietary, private software for free. The labor is free & now you're complaining that you'll have to pay a per-free-laborer fee for the infrastructure to manage all these free-laborers? I hope I'm missing something here...

You are jumping to a whole lot of conclusions there.

Re: Introducing unlimited private repositories

#546

Post by msbarnett »

Kratisto wrote: post #479
dreamsofdragons wrote: post #451

Earlier quoted context omitted.

I have, I'll continue to use bitbucket.

Any reason why? Just wondering.

GitLab's UI is pretty terrible, even compared to the not-so-great-either BitBucket UI.

GitLab's UI/UX is regressive to the point that when you visit a repo, you have to click another link just to see the damn sourcecode. It's as though they ignored every advance in source-code UX post-Sourceforge.

The stacked global and per-repo sidebars are confusing in a way that baffled me for several minutes, as well. They need a serious rethink of their UI/UX.

Re: Introducing unlimited private repositories

#547

Post by WillAbides »

StevePerkins wrote: post #521
WillAbides wrote: post #350

Earlier quoted context omitted.

> I don't want to leave Github, but now I have to, because I just won't get the approval to spend ~100's a month. No you don't have to leave GitHub now. GitHub isn't forcing existing customers onto the new pricing, and it says in the post that if that changes at least 12 months notice will be given.

What announcement are you reading? It states very clearly that this is the new pricing model, period. Yes, existing customers have a 12-month grace period before they're impacted by a price change... but that clock just started ticking. There isn't an indefinite opt-out for this model change.

I'm looking at this one [0]. Specifically this item in the FAQ:

> Will GitHub force me to move to per-user pricing after 12 months?

> No. At this time we are not enforcing a timeline to move and if in the future we do decide to set a timeline we are committing to giving you at least 12 months.

[0] https://github.com/blog/2164-introducing-unlimited-private-r...

Re: Introducing unlimited private repositories

#548

Post by [deleted] »

hunvreus wrote: post #130

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…

[deleted]

Re: Introducing unlimited private repositories

#549

Post by rhodysurf »

stonedge wrote: post #364
WillAbides wrote: post #352

Earlier quoted context omitted.

Check the bottom of this page [0] and prepare to be thrilled. [0] https://education.github.com/

This is only for the teaching/student aspect of academia. There's the whole business side of academia which is still a non-profit, still doesn't have any money, but for which the academic stuff doesn't apply.

They gave us free private repos for our organization when we were an academic research team building robots. It doesn't hurt to try.

Re: Introducing unlimited private repositories

#550

Post by msbarnett »

StevePerkins wrote: post #521
WillAbides wrote: post #350

Earlier quoted context omitted.

> I don't want to leave Github, but now I have to, because I just won't get the approval to spend ~100's a month. No you don't have to leave GitHub now. GitHub isn't forcing existing customers onto the new pricing, and it says in the post that if that changes at least 12 months notice will be given.

What announcement are you reading? It states very clearly that this is the new pricing model, period. Yes, existing customers have a 12-month grace period before they're impacted by a price change... but that clock just started ticking. There isn't an indefinite opt-out for this model change.

> Yes, existing customers have a 12-month grace period before they're impacted by a price change... but that clock just started ticking

"Will GitHub force me to move to per-user pricing after 12 months?

No. At this time we are not enforcing a timeline to move and if in the future we do decide to set a timeline we are committing to giving you at least 12 months."

So you have an indefinite period of time + 12 months, not a hard 12 months starting now.

Post reply on HN