We wanted to use Github at the (small) company I work for, but we have tons of tiny, low-traffic repos. Since Github limits repo count, regardless of how low-resource they are, we flat out cannot use them, period.

Bitbucket has the right idea - number of repos is completely meaningless. Make it unlimited and charge only by meaningful metrics, like user count. Unfortunately, their shift to that plan came too late for us, as we put in the effort of self-hosting. Still, there's that special something Github has that Bitbucket lacks, and we would still consider migrating to Github if only they dropped the arbitrary repo count limit.

I really don't like the response. git encourages a repo-per project, but github discourages it with their plans. This impedance mismatch means I don't use github for private hosting, only for open source projects, where there is no such mismatch.

On the other hand, organizations with a high dev tool budget are probably more likely, on average, to have more private repos. So it's in Github's best interest to charge by repo count, until they figure out a better way of discriminating between customers.

I love GitHub (and am a happy micro plan subscriber), but this deal just seems... well... kinda yawn.

You never know.

Exactly, so I might as well be committing to signing up for a paid plan.

EDIT: Not trying to be snarky, I'm a ridiculously happy micro subscriber, just don't see the real appeal of this...

Looks like there's a CSS bug on /account/billing - the coupon rows probably shouldn't change background colour on hover.

If I hadn't a micro plan already, I would definitely give it a try.

As a neutral observer (who did not downmod you, btw), your post did come across as oh-so-slightly whiney. I pay for Github. I don't care that they are offering Micro free.

What would be awesome is if they sent you a subscriber-only shirt after every 12 paid months or something, though. I don't actually use private repositories; I pay for the micro plan just to show my support :)

https://github.com/rails/rails/compare/v3.0.2...3-0-stable

Github Pages are really useful. Maintaining a project site is really easy when you can just create a gh-pages branch and push to it to update your site.

Also, network effects are undeniably part of the appeal. I'm much more likely to hack on a project or library if I can fork it on Github. It makes for a nice workflow.

Oh, and the interface is gorgeous, BitBucket's feels really tacky. There aren't many outages, and an outage has yet to actually affect me.

Just really happy with GitHub in general.

When you pay GitHub money, then you get non-public repositories.

Their copy-writing is first rate.

Should probably add that i would pay for a plan if i needed private repos, but this is nice since i get stuff i don't need and don't have to pay for. Freebies are awesome :-)

School projects tend to be proliferous and need to be private, which doesn't mesh well with GitHub. I'm mostly just paying them for a micro plan because I think the service is cool.

Anyway, cross-posting from the other thread:

> This is brilliant. Get tons of people who current just use GitHub for public repos to put up some private ones, then in a month send them an email saying "start paying, or we'll take away your private repos". People are lazy, so a lot of people once they've already put the repos up won't want to move them.

Inertia was working against them; this gets it working for them.

The initial setup can be quite challenging, but I found this guide to be quite useful: http://cjohansen.no/en/ruby/setting_up_gitorious_on_your_own...