News for hackers. Stuff that matters.
Re:GitLab Flow (2014) by Philipp__ on Saturday February 13, 2016 @05:02AM (#11093415)
Everybody is talking about GitLab these days but actually I am interested to see number of those who are ready to migrate to it for real... It still a lot of talk and little realization...
Re:GitLab Flow (2014) by ajdlinux on Saturday February 13, 2016 @10:19AM (#11094234)
At my very large and prominent employer, we use self-hosted GitLab locally, with Gitorious and GitHub Enterprise used in some other sections of the business.

Our local GitLab setup is rather recent and isn't quite a critical part of our infrastructure just yet, but I anticipate over the next few months we'll be switching more and more over to it. I recently started on a brand new project which is currently hosted on GitLab, though it'll probably move to public GitHub after we get approval to release it under a Free Software licence.

Re:GitLab Flow (2014) by nullified-vga on Saturday February 13, 2016 @10:39AM (#11094318)
I've been using GitLab at work for 8 months or so and we love it. It comes packed up with GitLAb-CI, which we use a lot, and Mattermost, a Slack clone. I'm hoping my boss will come to his senses and switch to Mattermost.
Re:GitLab Flow (2014) by nopzor on Saturday February 13, 2016 @11:40AM (#11094589)
Been following Gitlab pretty closely. At raintank we run a fairly large open source project on Github: Grafana. We're pretty frustrated with a lot of limitations on Github.

These limitations are becoming more painful as we grow our team, and deal with more issues across more repos.

Gitlab seems to be iterating pretty quickly. Github glacially.

For us, the killer feature that Github has is the network effect. We want to make it as easy for people to contribute code/collaborate on Grafana, and Github is where all the action (developers and code) is.

I suspect that many medium/large OSS projects have the same mindset.

Re:GitLab Flow (2014) by sytse on Saturday February 13, 2016 @12:42PM (#11094848)
We love Grafana, it allowed us to make GitLab.com issues three times faster this week https://gitlab.com/gitlab-com/operations/issues/42

I understand if you don't move to GitLab yet because of the network effect. Just so you know, GitLab allows people to log in with their GitHub account.

Re:GitLab Flow (2014) by johnmaguire2013 on Saturday February 13, 2016 @05:16PM (#11095890)
Even as a small OSS project, this is a problem for me. I've setup a mirror to Gitlab, but I'm keeping issues / milestones / etc. on Github still.

It's arguably even harder for small projects to switch to Gitlab -- Github is the main way people discover us. That's where people are looking.

Re:GitLab Flow (2014) by contingencies on Saturday February 13, 2016 @05:16PM (#11095889)
I have used it at two companies and am setting it up for one of my own right now. It's been mature to a useful extent for years, and is no doubt virtually a drop-in replacement for Github these days.

While I continue to host public projects on Github, my key reasons to host other projects on Gitlab are privacy, security, control, and availability. Pre-commit hooks (that can reject code) are awesome.

Re:GitLab Flow (2014) by DrRobinson on Saturday February 13, 2016 @07:59AM (#11093777)
At work we've been using self hosted Gitlab for more than a year and it works really great. Easy to use and maintain, would highly recommend.
Re:GitLab Flow (2014) by lerpa on Saturday February 13, 2016 @12:49PM (#11094866)
Been using the CE for more than a year. Works great.
Re:GitLab Flow (2014) by dijit on Saturday February 13, 2016 @05:08AM (#11093426)
I don't know, I moved everything I host off to my own instance of gitlab.

https://git.drk.sc/

You can still login with github or bitbucket, and there is a 'migrate project from ["github","bitbucket"], so, why not?

it even moves your issues over and such.

I did lose milstones on a few of my projects (where I used them) though.

Re:GitLab Flow (2014) by sytse on Saturday February 13, 2016 @12:50PM (#11094873)
Good to hear you're happy with your GitLab server. From GitHub we import repo's, issues, wiki's and merge requests. But not milestones as far as I know. I've created an issue for this https://gitlab.com/gitlab-org/gitlab-ce/issues/13421
Re:GitLab Flow (2014) by mpswardle on Saturday February 13, 2016 @08:08AM (#11093793)
We're planning on migrating a single repo to Gitlab hosted this weekend to try it out.

I'm hoping this can reduce some cost since i'm currently spending a lot on Github and Travis CI.

Re:GitLab Flow (2014) by sytse on Saturday February 13, 2016 @12:44PM (#11094853)
Cool that you'll give us a try. We're working to introduce mostly free CI Runners to GitLab.com. We already have a bunch but we're working on autoscaling them so there is less wait https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/...