BitBucket vs. GitLab.com
about.gitlab.com
about.gitlab.com
I think GitLab is great, but still prefer GitHub: no need to worry about hardware failures, or management. Someone does that for me, and does it well.
Regarding your second comment, you do not need to host your own instance if you don't want that.
You can host all your repos, public and private, for free at Gitlab.com. There are no limits, besides a 10GB limit for git annex and no restrictions to its usage.
If you're avoiding servers, that also means that you have different accounts for every SaaS service replacement you use, and administering permissions and accounts means a lot of extra and pointless labor.
Using custom code to facilitate your business' processes -- such as server-side plugins for things like your source control -- becomes impossible.
Business processes become dependent on SaaS + data dependence that can't easily be exported from the SaaS services, and you're paying out the nose for them every month -- locally licensed software is cheaper, for quite obvious reasons, all across the board.
All so that you can avoid a once-in-N years failure of a hard drive and running apt-get?
No thanks. That's an insane cost/benefit analysis.
Server administration should be easier than it is, but it's not hard, and I'm not about to make every other business process worse just to avoid it.
* No private repo in the free plan
* Pricing per repo in the paid plan - probably fine for a startup with just a couple products, unusable for a service company that starts a new project every month
So if you care about private repos, BitBucket vs GitLab is interesting.
Thanks to the GitHub designers for saving GitLab a lot of work, I guess? Most of the GitLab design, almost all of the abstractions and interaction patterns, and even some of the UI text comes straight out of GitHub.
I don't think this is necessarily a bad thing, but GitLab feels like the webapp version of one of those GPL clones of a Microsoft app.
I'm sure everyone has inspirations, but a quick look at GitLab and GitHub makes it clear that the two have diverged considerably in terms of design.
Lastly, we do believe that we have much to learn in terms of design and UX. We'd love to receive contributions and concrete feedback that help us with this.
As another side question, suppose I sign up for a GitLab account and have repositories there. Is it possible to import / move them easily if I later decide to host my own instance? I noticed that you said it's easy to migrate from Bitbucket / Github, but can repos be moved between GitLab instances easily?
> As another side question, suppose I sign up for a GitLab account and have repositories there. Is it possible to import / move them easily if I later decide to host my own instance? I noticed that you said it's easy to migrate from Bitbucket / Github, but can repos be moved between GitLab instances easily?
If you have a large amount of repositories, you can import them directly, rather than simply pushing them to the new server. Of course, we're happy to help you with this if needed.
Way back when I was looking at both (7 years ago maybe?), it seemed that mercurial's main selling point was functional equivalence to git with a "better" architecture and source language. This is the ultimate case study in the fact that neither of those things matter to users (even deeply technical users) unless they impact user experience (stability, performance, UI, etc).
[1]: http://en.wikipedia.org/wiki/Git_(software) [2]: http://en.wikipedia.org/wiki/Mercurial
We're working hard at making GitLab feel better, by spending more time on design and UX, taking inspiration from Slack and Apple.
We'd love to get feedback on this.
Why don't GitLab & BitBucket instead collaborate, for example by producing a decentralized & offline-capable version of GitHub's key features (issues, pull requests)?
Once you're #1 and #2, then you can turn your guns on each other!
We also published about us vs. GH: https://about.gitlab.com/2015/01/20/github-enterprise-vs-git...
and even have a page on our site dedicated to it: https://about.gitlab.com/better-than-github/
In terms of comparing us to #3, we want to show everyone, not just people using GH, what GitLab is. This helps people finding us.
Of course that might not be a sustainable state of affairs in a big picture sense, but it works for us for right now.
For me to migrate I'll have to upgrade to the minor versions until I get to the latest. Thats a huge pain. Is there any other way?
What happened that you go so far behind in versions?
For example we had a brief crisis because we deleted branches after merging them into dev and found that we needed to rewind and merge them again. It took considerable research to figure out how to resurrect a branch from the reflog and finally from just the log, where we discovered subtleties like --no-ff that added friction (or at least the fear of it).
Why don’t these sites simply provide GUIs for common tasks like rewinding, undeleting branches/files, as well as the countless other things that users need?
We use the feedback intensively to improve GitLab.
On top of that, we have some awesome features that put us ahead of GH: https://about.gitlab.com/better-than-github/
1. Put free price / comunity product on price plan
2. Provide simple guide and script to convert existing bitbucket hg to git (because people are lazy)