If your team is small enough then BitBucket is a great option for closed-source projects. The only difference is the lack of GitHub's interface and neat features like graphs. I wasn't too impressed with the code-review features for pull requests, but I don't remember GitHub being significantly better either.
Why the World Needs Another Git Repository Hosting Service
31–40 of 49 posts
Re: Why the World Needs Another Git Repository Hosting Service
#32And if you want to host it yourself, these look like promising competitors: http://gitlabhq.com/
I set this up at my university to see if it would be a good solution for school-related project hosting. Haven't rolled out (yet), but as you said it's very promising.
Re: Why the World Needs Another Git Repository Hosting Service
#33When I was in College (just graduated a few months ago), GitHub applied a $7 coupon to my account, which covers a micro account. All I did was ask about student pricing. They should probably offer an educational discount with .edu email verification.
Re: Why the World Needs Another Git Repository Hosting Service
#34A totally different way to think about this post, is that the guy who has posted this post is a bitbucket fan or a clever promoter, so he has listed every point that makes BitBucket differ from Github and is the reason, why it is loved by a lot of guys out there.
If I am correct in my guess, then I really think its a great marketing strategy, and if not then BitBucket guys should really think of marketing in this way.
Re: Why the World Needs Another Git Repository Hosting Service
#35You know github gives free private repositories to students right?
Re: Why the World Needs Another Git Repository Hosting Service
#36Come on, there are many options in the market that suits well in every mentioned need, just to point, http://www.codeplane.com just right the same thing.
Ok, you can create a new service, but you shouldn't act like you're the only one around that do what you do.
Re: Why the World Needs Another Git Repository Hosting Service
#37If you want private repo hosting on the cheap, I would suggest using Gitolite [1] on a VPS [2].
The current version includes self-service key management, regular users are able to create repos in their own namespace, and easy forking of repositories. It's extensible, you can write your own commands in any language.
Granted, it has minuses. It only has a command line interface (no GUI), requires a little setup and editing of configuration files and reading of docs.
Re: Why the World Needs Another Git Repository Hosting Service
#38Earlier quoted context omitted.
4. put repos in dropbox folder (5. have repo world readable when security fails)
6. Walk on eggshells as to not accidentally delete your repos chilling in userspace (everyone's had this experience at some point with Dropbox files)
Dropbox does have a limited form of version control fwiw. Select a file on the website and there's a "Previous Versions" item highlighted.
Not that I'm recommending this approach. That side, I do have GitHub repos that are also in my Dropbox, so I can collaborate with non-technical folk. It works great and haven't had a single issue with it in about 6 months of usage.
Re: Why the World Needs Another Git Repository Hosting Service
#39If you really want to pay only for the I/O you're using, just spin up an EC2 instance and install GitLab ( http://gitlabhq.com/ ).
Wouldn't you then be paying for the EC2 instance's idle time in addition to the I/O you're using?
Re: Why the World Needs Another Git Repository Hosting Service
#40I would imagine that these guys are very sad and depressed right now, given all the harsh -- and correct -- feedback that they've gotten here. I'll try to add something different:
The various competitors in this space compete apparently on public/private visibility, price, storage quotas, and user+repo counts. If you compete on these dimensions you will have a very difficult time differentiating yourself -- there simply is not enough difference between one repo provider and another on these bases to matter. Cost of switching, I would imagine, is relatively easy -- `git remote add`, `git push`, and done?
There is also, perhaps, competition on UI/UX quality. This can be a differentiating factor for some, but I think not as strong as it is for other markets, given the strong technical background of the target market. If you had some original and compelling offer which had a poorer but workable UI (which improved rapidly over time), that could negate the advantage that e.g. Github has over you on interface.
I don't have any better ideas for this space -- the generic advice for you I would give is to innovate in some different, not-already-explored way. Can you provide something completely different from more users, more repos, more storage, lower price?