Comment by pvorb
10 years ago
The problem is that GitHub has a monopoly and is considered _the_ current standard for Open Source. But I think that once some of the major projects move to alternatives like GitLab (which has many of the features described in that letter) GitHub will have to obey its user base. Unfortunately no Open Source project with a large user base will dare to do the first step.
There are some open source projects with a large user base taking the step to us, for example https://gitlab.com/mailman/mailman
Regarding the three demands in the doc:
1. GitLab has issue templates in EE and on GitLab.com https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/28
2. GitLab has the award emoji function that doesn't spam and acts as a voting system https://about.gitlab.com/2015/11/22/gitlab-8-2-released/
3. We're open to displaying CONTRIBUTING.md more prominently, please open an issue on our public issue tracker that contains all our planned features https://gitlab.com/gitlab-org/gitlab-ce/issues
I'll go sleep now but please ask any questions so I can respond tomorrow.
Yes, I already saw some of these.
Unfortunately, there's no Travis CI integration yet, which I've been using on GitHub a lot.
I'm evaluating GitLab CI right now. Am I right, that I have to host a runner myself if I don't want to use a shared runner for my project?
> You can setup as many runners as you need. Runners can be placed on separate users, servers, and even on your local machine.
Does "local machine" really mean a non-public machine like my notebook?
Appreciating help from GitLab's CEO :)
We would love for Travis CI to offer support for GitLab, they can use our new commit status API.
But you'll find that GitLab CI is a pretty complete replacement. If you don't want to use a shared runner you indeed have to use a shared runner.
Running on your local machine can indeed include your notebook.
2 replies →
We're working on a response to all the issues in the letter in https://gitlab.com/gitlab-org/gitlab-ce/issues/8938
We've published our response https://about.gitlab.com/2016/01/15/making-gitlab-better-for...
I went ahead and created an account on GitLab.com. So far I can tell the transition is seamless. You can import a repository from GitHub with only a few clicks. Issues will be inherited, but the single PR on the repo I tried to migrate got lost on the way.
Importing Pull Requests will be possible with the next version of gitlab that's going to be released on the 22nd january. See this MR for more information: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2168