Live data from Hacker News

Introducing unlimited private repositories

github.com

491–500 of 662 posts

Re: Introducing unlimited private repositories

#491

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…

Meanwhile many use BitBucket free private repos for years and are very happy about it.

Re: Introducing unlimited private repositories

#492
post #439
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…

I've used Bitbucket in the past. They charge per-user[1], and their pricing is significantly better free for 5 users and then once you eclipse 5 users it's $1/user up to 100 users and then $200 for unlimited users. [1] - https://bitbucket.org/product/pricing

This. I use bitbucket too and I can't understand why people are still paying github when bitbucket does exactly the same and is free.

Re: Introducing unlimited private repositories

#493
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…

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

Nonprofits need CRUD apps just like any other organization.

"Being a nonprofit" doesn't mean "developing open source software".

Re: Introducing unlimited private repositories

#494
post #269

Earlier quoted context omitted.

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…

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…

For non-profits, you could reach out and see if they'd do something special for you. I used to work in for a higher ed institution and they were gracious enough to give me a free account.

Re: Introducing unlimited private repositories

#495
post #492
post #439

Earlier quoted context omitted.

I've used Bitbucket in the past. They charge per-user[1], and their pricing is significantly better free for 5 users and then once you eclipse 5 users it's $1/user up to 100 users and then $200 for unlimited users. [1] - https://bitbucket.org/product/pricing

This. I use bitbucket too and I can't understand why people are still paying github when bitbucket does exactly the same and is free.

Github does seem to be the gold standard for open source projects.

Having said that, I used to pay for Github's personal plan and found the cap on private repos (5 when I subscribed) to be a little too limiting. I ended up canceling the subscription and using a Bitbucket free account for private repos and Github for public repos.

After using Bitbucket for a while, I think if I had to upgrade to a paid service, I'd just stick to Bitbucket.

Re: Introducing unlimited private repositories

#496
post #269

Earlier quoted context omitted.

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…

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…

[deleted]

Re: Introducing unlimited private repositories

#497
post #475

Earlier quoted context omitted.

GitLab CE (Community Edition is Free) and is truly great we use it in our own internal software development process. However for a bigger enterprise they require more functionality here is a comparison of the differences between the Community and Enterprise Editions. https://about.gitlab.com/features/#compare Several pricing options for EE but essentially the base cost is $39 /year per user. https://about.gitlab.com/…

gitlab.com runs EE though doesn't it? You only need to pay if you want self hosted EE.

I've only ever seen the trial but I could be wrong!

Re: Introducing unlimited private repositories

#498

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…

> But I'd appreciate if their PR department didn't expect us to swallow this as a positive change. Most coders understand basic maths.

If you don't like PR, then why can't you just see past it? Why wouldn't an organization try to make it sound like a positive change? Do you expect them to come out with negative changes?

What does valuation or organization changes have to do with this anyway? Are you somehow unhappy with their company? Sure they have issues but they have also created a great platform with lots of networks effects and value. It works, and it's very cheap for what it does. And if you don't like it, there are tons of competitors.

Seriously, what's the problem here?

Re: Introducing unlimited private repositories

#499
post #475

Earlier quoted context omitted.

GitLab CE (Community Edition is Free) and is truly great we use it in our own internal software development process. However for a bigger enterprise they require more functionality here is a comparison of the differences between the Community and Enterprise Editions. https://about.gitlab.com/features/#compare Several pricing options for EE but essentially the base cost is $39 /year per user. https://about.gitlab.com/…

gitlab.com runs EE though doesn't it? You only need to pay if you want self hosted EE.

It does, yes :)

Re: Introducing unlimited private repositories

#500
post #378

Earlier quoted context omitted.

Git is just a format for storing data with a record of how that data changed. Saying you shouldn't store it in git seems rather like saying you shouldn't store it in btrfs. It's true that if your btrfs disk image becomes public, the data is recoverable, and it's hard to reliably scrub deleted files from btrfs, but that doesn't mean it's the wrong tool for a filesystem (or a repo) that stays entirely internal. Saying…

> Saying you shouldn't store it in git seems rather like saying you shouldn't store it in btrfs. Best practice is to avoid storing secrets in plaintext, or sharing secrets between users/roles. Yours isn't an argument in favour of git, it is an argument against btrfs. (I don't have any problem with storing passwords in that way, I'm just pointing out why it's not the best practice.)

> Best practice is to avoid storing secrets in plaintext

How do you store them, then? If they're encrypted with a password, how do you store that secret?

I'm pretty sure best practice is in fact to store things like SSL private keys, cookie HMAC secrets (e.g. Django's SECRET_KEY), and so forth on local disk unencrypted, protected by only filesystem permissions (and the host OS as a whole protected with standard means). In fact I'm not even sure it's possible to store OpenSSH private keys unencrypted.

> or sharing secrets between users/roles.

There's only one role here: the application that has an API key. There are multiple developers of that application, and possibly multiple instances of that application, but it's a single role.

Post reply on HN