Live data from Hacker News

Moving to GitLab: Yes, it's worth it

about.gitlab.com

181–190 of 356 posts

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

#181
post #132

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 think that's a bit of a simplistic way of looking at it. There's an easy explanation of why this approach exists though, if you agree with the following statements:

- Race, gender, sexual orientation, disability etc. do not generally affect an individual's skill as an employee

- People from certain groups are under-represented in the industry

- Under-representation generally reflects an underlying problem somewhere, because one would expect various groups to be represented broadly in line with wider society

- One of the problems that can cause under-representation is an existing bias in an industry, which can discourage other members of a group

- One of the approaches to solving this is to help ensure that those groups feel comfortable in the industry

- One of the approaches to helping them feel comfortable is to ensure that communities are inviting, open-minded, and aware that things they say or do may upset or discourage other people, even though they are do not find those things offensive themselves.

It's about observing a trend which seems wrong for various reasons, and attempting to help solve it. I don't doubt for a second that many people go completely overboard on this issue, but outright rejecting any attempt at using, say, gender-neutral language in open-source projects just seems to go completely in the other direction.

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

#182
post #23

Phabricator is a great alternative, by the way. Really stable and has the best code review interface / workflow I've ever used.

I really want to love phabricator, but the local install for a new team is so painful... any thoughts about how to make that better?

Everyone is talking about installing these services. Don't they have a central hosted server like Gihub?

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

#183
post #121

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.

I actually assumed that this message was automated – "We found on objectionable word in your project, please don't use it."

It just seems that this problems is remarkably easily solved with a simple "We are using a technical term correctly, maybe you should consider adjusting your automated emails."

I do get the impression that people generally seem to be all to eager to take offence, and it strikes me as a bit ironic to flounce off in a huff as a result of a badly-judged automated process!

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

#184

As always, we're happy to answer any questions about GitLab.

Why do you offer hosted EE gitlab free? I mean I love it but that seems to run counter to keeping gitlab around. In fact there seems to be no way at all to pay for gitlab, without having to host a local install.

Most of the market revenue is concentrated in on-premises/single-tenant installations, also see https://about.gitlab.com/gitlab-com/#why-gitlab-com-will-be-...

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

#185
post #23

Phabricator is a great alternative, by the way. Really stable and has the best code review interface / workflow I've ever used.

I really want to love phabricator, but the local install for a new team is so painful... any thoughts about how to make that better?

Package it as a docker container.

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

#186
post #153

Earlier quoted context omitted.

Just to be clear, you're saying: "If large company x hires a single incompetent person, that is a good reason to never deal with said company again." I think that's the parents interpretation of OP and hence the "seems like a disproportionate response." (I agree it was absurd to flag the content).

That's oversimplification. Even if it is just her own personal incompetence, if GitHub just hired her and let her loose as some kind of independent repo ombudsman to scold users, then yeah, that's a terrible management decision that warrants reconsidering your relationship with them.

We don't even know the whole story. The "woman" who sent the note is most likely just be an automated script.

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

#187
post #145

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.

I stopped using Github when they hired blatant racists as part of their 'social outreach' team. The infestation of politically-correct politics drives talent that can't be bothered with such cruft away. I was there to code. Not worry about if I hurt some oversensitive person's feelings for referring to master/slave copies.

I wrote this elsewhere so I won't repeat it here (https://news.ycombinator.com/item?id=12232883)

We're all on Github to write code, but I'd argue you are dangerously close to throwing the baby out with the bathwater there. It seems perfectly reasonable for someone to say "hey, this term you use might be offensive/makes me uncomfortable, please consider changing it." It's also perfectly legitimate for you to say "I don't want to do that".

I just kind of wish that everyone would be a little less sensitive about the prospect of other people being offended by things that they are not. Political correctness, in the sense of "try not to say things that are offensive" sense, is probably not the worst idea in the world!

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

#188

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.

We've been using https://rhodecode.com for internal repositories: it is also open source, yet has better interface and out-of-the-box LFS support.

The native subversion and mercurial support for the same repos is incredibly attractive. Any idea how it converts them to a shared format in real-time?

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

#190
post #125

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!

Could you take a look at price for GitHub for same big team please?

Sorry, that was my point – Github is ~ $11k for a team of 100 developers. The difference between '$11k' and 'free' is basically irrelevant when you are paying > $25m for your engineering team in the first place!
Post reply on HN