Re:Why GitHub’s pricing model stinks (for us)
by d0m on Wednesday February 13, 2013 @06:29AM
(#5212547)
Or the client can pay for it. I.e. add x$/mo to the maintenance cost for "code hosting" or whatever.
Re:Why GitHub’s pricing model stinks (for us)
by nicholassmith on Wednesday February 13, 2013 @06:37AM
(#5212569)
Or that, it is technically a per project expense.
We all want things to be cheaper, but sometimes you need to rationalise things off and realise whilst they emotionally look expensive, they're actually really not when you work out what the cost is to you in terms of work to cover it.
Put it this way, if you go to BitBucket (they're great as well! Highly recommended!) you'll save money, but lose the headline features of GH. For you this may or may not be a big problem. If you go down the self-hosted route (super valid!) then you've got a specific amount of admin time that needs to be put in per month by either a dev or sysadmin and that's more than likely to either cost the as much or more than GHs pricing.
Pricing is hard, but GitHub is pricing where GitHub needs it's prices to be.