12 ms·
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 t
by cstejerean 10y ago
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 repos, but those can stick with the old model for a while (at least 12 months). And in the meantime GitHub may adjust their model to accommodate those situations too.
Lastly, this is a huge freebie for individual accounts that now get unlimited repos for $7/month. That will benefit a lot of people.
So I don't see this as PR spinning, but rather as an overdue move on github's part to a model that makes a lot more sense and benefits small organizations and individuals.
- odonnellryan 10y ago> This is a good deal for small organizations that like to have many small repositories (for internal libraries, utilities, micro services, modules, etc). I'm a small contracting shop: makes more sense to me. I might have 100 repos, but I can only develop so fast. Now all I'm costing GitHub is a little diskspace (which is insanely cheap, especially for text).
- asher_ 10y agoI couldn't agree more. It has annoyed me when companies charge more for decisions about how you choose to do something - in this case how you split up your code. Paying per person makes much more sense.
- endymi0n 10y agoThis was exactly the reason we used Bitbucket in the beginning, even if it was worse in some aspects. Github would have been simply too expensive (or restricting) with our "it's always in source control" approach, even for smaller prototypes. We're happy Gitlab users now by the way - and I'm curious how long Github will survive with their over-valuation as the alternatives get seriously better now - the lock-in and network effects are quite shallow IMHO.
- sytse 10y agoJust wanted to add that if you don't want to run GitLab yourself our GitLab.com is free with unlimited private repositories but it also has also unlimited private collaborators https://about.gitlab.com/gitlab-com/ https://about.gitlab.com/gitlab-com/
- ciokan 10y agoAny API on this service?
- sytse 10y agoSure, see http://doc.gitlab.com/ce/api/ http://doc.gitlab.com/ce/api/
- ciokan 10y agoThe interface is horribly (painfully) slow. On the API side...any of the params I post when hitting the create project endpoint are not taken into consideration. With the following data posted to the API I still get public builds, issues not enabled, wiki not enabled and so on: {'issues_enabled': True, 'description': None, 'visibility_level': 0, 'public_builds': False, 'wiki_enabled': True, 'snippets_enabled': True, 'merge_requests_enabled': True, 'name': 'testfoo'}
- johntash 10y agoI never realized gitlab.com offered free private repos. Thanks!
- spraak 10y agoBest reply ITT
- fps 10y agoI work for a non-profit open source organization that collaborates on github (https://github.com/edx/ 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 look at other alternatives. Github's code review tools are already pretty mediocre compared to other tools like gerrit, and we've long since moved off of github issue tracking due to lack of features compared to JIRA.
- jnmandal 10y agoIf you are non profit and open source do you really need private repos?
- fps 10y agoWe have about 100 private repos at the moment, including internal tools, branding related components, infrastructure code and pre-release stuff that we're not developing in the open. We may just move those to AWS code commit, gitlab or gogs and switch back to a free org.
- Q6T46nT668w6i3m 10y agoFWIW, I work for an academic non-profit and we use public repositories with an appropriate LICENSE. We like it because we don't need to manage read permissions.
- VLM 10y ago"that we're not developing in the open" Honest question... why? I totally understand the mindset of "gotta go all secret squirrel to protect our profits" but if your org isn't in it for the profits there's not much to protect? I have seen examples of people performing very naughty acts like private repos to hold plain text passwords, plain text cloud service keys, plain text corporate credit card numbers for expense payments, etc.
- blktiger 10y agoIf you want unlimited private repositories, just use bitbucket instead. It's free instead of $7 a month.
- vidarh 10y agoI've personally stuck to Bitbucket for all my private repositories exactly because Githubs pricing model made it untenable. For that price I might just sign up, even though I might keep syncing to Bitbucket anyway, just because I'm paranoid.
- Alupis 10y agoMy 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.
- giovannibajo1 10y agoThe new pricing model is about 9x more expensive than Bitbucket, for a given number of users. If your cost-concerned, I can't understand why you should reverse your decision.
- Alupis 10y agoWe have a fairly small team of developers, and a fairly large number of private repositories. So, for us, it's a pretty significant savings.
- hrez 10y agoPrice per idle/obsolete etc repo - $1.5-$2.5/month and goes down with number of repos. Price per idle/noncontributing user - $9/month and it stays constant. In any case, for my org it would mean ~5x cost increase. So yes, nice spin.
- Thirdegree 10y ago> Lastly, this is a huge freebie for individual accounts that now get unlimited repos for $7/month. It's also nice for student, like myself, who get unlimited private repos for $0 a month.