3 ms·
Things that make me not use gitlab (some of them are super shallow, stupid and relatively unfounded): 1. They used to use Azure, so even though I know Azure is
by sam0x17 7y ago
Things that make me not use gitlab (some of them are super shallow, stupid and relatively unfounded):
1. They used to use Azure, so even though I know Azure is actually an awesome cloud platform, I get this mental image of "Microsoft MVPs" constructing gitlab using VBScript macros because I come from the M$ era.
2. the very public data loss that happened a few years ago, that sounded like a mess, gives the lasting impression that repos are not lasting if they are in gitlab.
3. I never knew gitlab didn't just look like bitbucket, which I hate. In fact, I never would have looked at all if I wasn't writing this response, so I guess to get me they would have to lead with "Nothing like bitbucket!!"
4. I've spent so much time in github, that anything even slightly different pisses me off.
5. The logo looks like firefox porygon edition. GitLab is such a cool name, it could have a better logo, like the word "Git" followed by a chemistry beaker / "potion" thing.
6. The only marketing that would ever work on me would be "has an interface identical to github, does all the things github does, plus these 30 other things". Most of their marketing leads with the "30 other things", so I click away before I bother to read it.
7. If GitLab or anyone tried to do something innovative like writing an extended version of git that adds comments and pull requests to the underlying CLI, and bakes them into the repo itself in some way so we can just stay in CLI world all day, I'd be absolutely onboard, but no one does that for some reason even though that would be a huge differentiator. A similar strategy worked for Heroku if you think about it.
8. Every single open source project I use or contribute to uses github. If GitLab were to, say, add a github integration that lets me work with all the github repos I care about, but using Gitlab's UI, I would be intrigued.
- emilycook 7y ago> 8. Every single open source project I use or contribute to uses github. If GitLab were to, say, add a github integration that lets me work with all the github repos I care about, but using Gitlab's UI, I would be intrigued. This does exist: https://docs.gitlab.com/ee/user/project/import/github.html#mirroring-and-pipeline-status-sharing https://docs.gitlab.com/ee/user/project/import/github.html#m...
- brodock 7y agoDepending on what you consider "work with github repos" here, you can import then as emily said above, and setup a push mirror, so whatever you do on gitlab is pushed back to Your fork on GitHub, so you can do PRs there. The way to interact between the two without this sort of functionality would be if both agreeded in some sort of federation access. I don't see GitHub allowing that anytime soon, as that would reduce their lock-in effect. We have an epic for Distributed Merge Requests: https://gitlab.com/groups/gitlab-org/-/epics/260 https://gitlab.com/groups/gitlab-org/-/epics/260 and an issue to discuss ideas about Federated GitLab: https://gitlab.com/gitlab-org/gitlab-ee/issues/6468 https://gitlab.com/gitlab-org/gitlab-ee/issues/6468
- sam0x17 7y agoYeah mirroring is relatively easy. What I want is full and continuous synchronization of everything -- comments, PRs, etc. You could do it with a combination of the Github API and a web spider, at least with public repos.
- sam0x17 7y agoYeah importing doesn't do it for me though. I know I'm not going to be able to get any people to go to my repos if they are on Gitlab. But if I could use Gitlab as the UI, that would be cool, and might be the start of something that would get me to eventually host things on Gitlab.
- emilycook 7y agoYeah that's fair, and we're pretty aware that we don't have e.g. the social functions that GitHub has. Your comment has sparked some internal discussion though, a full integration would be interesting.
- sam0x17 7y agoOn that note, legally, I don't think there is anything preventing you from automatically mirroring all MIT-licensed repos as well and pulling in some organic search engine traffic that way. Don't know if that also applies to the comments, pull requests, etc., but it's an intriguing move and definitely one I'd consider as long as there is a sane way of allowing the relevant users verify their ownership of a repo via GitHub API if they wish to "claim" the corresponding automatic gitlab repo.