Moving to GitLab: Yes, it's worth it • Hacker News Board

Re: Moving to GitLab: Yes, it's worth it

#161

Post by allemagne » Fri, Aug 05, 2016, 2:43 PM UTC

favadi wrote: post #132

AWildDHHAppears wrote: post #111

Interesting. For projects that don't need a "community" we've been using Amazon CodeCommit. We don't like to use Github anymore because of the politics there. Example: We had a project involving software filters that included this sentence in the description: > Phase is related to time, but a pure time delay does not involve any phase shift. A pure time delay or "group delay" is constant with frequency. Phase shift v…

I find that github's point of view on those problems are very hard to understand. For example, I once read a github's blog complaints that they don't have enough black, women leaders in github company. But if they really think all races/genders are equal, why they care about how many percent of leaders are non-white, or women?

I'm confused by your question. A lot of organizations have similar concerns. Do you believe that all discussion of diversity is equally nonsensical, or is there something about Github's stance that strikes you as especially so?

Re: Moving to GitLab: Yes, it's worth it

#162

Post by dijit » Fri, Aug 05, 2016, 2:44 PM UTC

Zecc wrote: post #114

krautsourced wrote: post #32

I really liked Gitlab when last I tried it, but in the end I went with https://gogs.io/ instead. For a small-ish team this felt like the most straight forward self-hosted solution. Still missing LFS though, which sucks, but it's being worked on.

I couldn't help noticing Gogs is hosted on GitHub... https://github.com/gogits/gogs

I don't know how to feel about that, on the one hand it's "not using the soap you're selling" and makes you seem disingenuous about the quality of your product.

However, it is the "home of developers" right now, and they probably would prefer a low barrier to entry for people to get involved.

Re: Moving to GitLab: Yes, it's worth it

#163

Post by olejorgenb » Fri, Aug 05, 2016, 2:45 PM UTC

krautsourced wrote: post #32

I really liked Gitlab when last I tried it, but in the end I went with https://gogs.io/ instead. For a small-ish team this felt like the most straight forward self-hosted solution. Still missing LFS though, which sucks, but it's being worked on.

Wow, that UI is VERY similar to github: https://try.gogs.io/sigf/test

Re: Moving to GitLab: Yes, it's worth it

#164

Post by favadi » Fri, Aug 05, 2016, 2:46 PM UTC

scaryclam wrote: post #156

favadi wrote: post #138

Earlier quoted context omitted.

Last time our team tried gogs, it is unusable. Some very important features are missing: - code review - deployment key And the builtin SSH server will randomly hang once or twice every day.

Gogs has had both those for quite some time now. We did a comprehensive internal review of both gogs and gitlab. Gogs was a long way ahead of gitlab in terms of stability/speed and had pretty much all of the features developers tend to need.

Can we comment on a specific line in a merge request with gogs now?

Re: Moving to GitLab: Yes, it's worth it

#165

Post by matthewmacleod » Fri, Aug 05, 2016, 2:46 PM UTC

danielrmay wrote: post #124

matthewmacleod wrote: post #118

GitLab is great and it's lovely to see a diverse selection of tools, but I'm not too convinced of the cost benefits – for a team with 100 developers, the annual cost of ~$11,000 is a pretty small amount compared to the maybe $25m salaries you'll be paying!

Avg salary of $250k per dev? Are you hiring?

I would guess fully-loaded cost is 2x salary, so perhaps I should have said "amount you'll be paying for staff" :)

Re: Moving to GitLab: Yes, it's worth it

#166

Post by connorshea » Fri, Aug 05, 2016, 2:46 PM UTC

tomjen3 wrote: post #140

Gitlab is pretty awesome, especially because they let you have unlimited private repositories on their website. So far my biggest annoyance is that when you click on a project you don't get a list of files (like you do on github) but just the projects readme, and even then only if you remembered to capitalize it.

In Settings you can set the "Project view" to Files view and it'll give you what you're looking for :)

https://gitlab.com/profile/preferences

Re: Moving to GitLab: Yes, it's worth it

#167

Post by tedmiston » Fri, Aug 05, 2016, 2:48 PM UTC

pille wrote: post #121

matthewmacleod wrote: post #112

Earlier quoted context omitted.

We removed our project and never used github again. That seems like a totally disproportionate approach versus responding with a polite 'this is a legitimate use of the word, thanks' message.

Maybe she actually could've read the text and figured it out herself before sending out the note? Just firing off a warning based on a simple text match seems high-handed and/or incompetent enough to consider leaving.

Presumably it was an automated message.

Re: Moving to GitLab: Yes, it's worth it

#168

Post by cookiesboxcar » Fri, Aug 05, 2016, 2:49 PM UTC

lima wrote: post #148

Karunamon wrote: post #142

Earlier quoted context omitted.

I have this problem too. It's not hard to set up, there are just so many tiny pieces that need to be run by hand that it's going to take a human well over an hour to read through the docs and get it right. Someone made a Saltstack state[1] that I've used and had some success with - installing and configuring Salt from zero and using this config is still faster than installing Phabricator by hand. [1]: https://github.…

It's actually much easier to setup and operate than GitLab with its massive dependencies. Also a lot faster.

I'm talking specifically about the client tool arcanist, which IMO is the real benefit of Phabricator

Re: Moving to GitLab: Yes, it's worth it

#169

Post by tedmiston » Fri, Aug 05, 2016, 2:50 PM UTC

dijit wrote: post #160

I posted before[0] about why I moved to gitlab; I'm using a self-hosted instance and the only real complaint I have is resource consumption. But if you bite the bullet a bit it's a really great product. The other thing would be "ease of deployment" or lack thereof- if you're going for anything other than omnibus installs or docker images then it can be a bit painful. (I wanted to run on freebsd for example). But, yes…

Similar view for myself; though the resource consumption is such a minor complaint that I don't even really consider it relative to all of the benefits GitLab provides.

Re: Moving to GitLab: Yes, it's worth it

#170

Post by haynes » Fri, Aug 05, 2016, 2:50 PM UTC

dijit wrote: post #160

I posted before[0] about why I moved to gitlab; I'm using a self-hosted instance and the only real complaint I have is resource consumption. But if you bite the bullet a bit it's a really great product. The other thing would be "ease of deployment" or lack thereof- if you're going for anything other than omnibus installs or docker images then it can be a bit painful. (I wanted to run on freebsd for example). But, yes…

How has your experience of installing gitlab on freebsd been? Anything in particular that can be improved? I'm pretty sure the gitlab team is open for all kind of improvements. :)