Earlier quoted context omitted.
My point is that larger companies are now be punished for a failed initial pricing model by GitHub. I prefer the new pricing model from a personal point of view, but for larger organisations it's now too expensive and I think many will relocate their repositories to BitBucket, or GitLab, or Gogs, or etcetera. Edit: My parent post is being down voted and that's fine, my point was not made in anger, it was an observati…
> a failed initial pricing model by GitHub It's been 8 years since they revealed their pricing model, which has remained mostly unchanged on the lower end and only adjusted on the high end to account for GitHub Enterprise and suggest people move to that instead of the gargantuan $3k/mo plans. I don't know many SaaS companies that don't tweak their pricing much more infrequently than that. Thoughtbot's Giant Robots Sm…
Introducing unlimited private repositories
431–440 of 662 posts
Re: Introducing unlimited private repositories
#432Re: Introducing unlimited private repositories
#433Earlier quoted context omitted.
god beware if your open source project needs a single private repository to share passwords between admins for example or private config for your webserver. Suddenly you see yourself at 394$ compared to the 7$ you paid before.
I hope that any team using github to share passwords is driven to move away from that method because of this price change. That's a bad bad idea.
Re: Introducing unlimited private repositories
#434Earlier quoted context omitted.
Why don't you just add the SSH public keys of your CI machine to your own GitHub account?
I wouldn't want a CI to store a key that has R/W access to all my repos in all my organizations. I'm in at least 5 active organizations that I would be putting at risk
Re: Introducing unlimited private repositories
#4351. 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…
Re: Introducing unlimited private repositories
#436Earlier quoted context omitted.
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
#437Re: Introducing unlimited private repositories
#438Earlier quoted context omitted.
Isn't that one of the points of marketing: Highlight issues as a positives to decrease their impact to sales? ps. No pricing model will suit every org. The current model based on repo numbers has horrid steps which make no sense. eg. 125to300 private repos = $200to$450 cost. So if you need 126 repos you pay more than twice as much for that extra 1 repo. That makes little sense to me.
yes, but you are comparing apples to oranges. If you had to jump from 125 to 300 users in ONE step as per the current pricing model instead of paying only for the marginal next user. Recognizing the repository steps are a pain for customers and not moving towards a pricing per _single_ repository, say between 1$ or 2$ per private repository - is just plain misleading. They could have still thrown in the personal plan…
To me, give a per user or private repo cost. Allow the customer to choose between user or repo model, each addition costs a single fixed unit. Simple!
Re: Introducing unlimited private repositories
#439Earlier 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…
Re: Introducing unlimited private repositories
#440Earlier quoted context omitted.
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.