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

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

#141

Post by GFK_of_xmaspast » Fri, Aug 05, 2016, 2:17 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?

Don't be tiresome.

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

#142

Post by Karunamon » Fri, Aug 05, 2016, 2:18 PM UTC

cookiesboxcar wrote: post #92

lima wrote: 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?

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.com/bougie/salt-phabricator-formula

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

#143

Post by tomjen3 » Fri, Aug 05, 2016, 2:21 PM UTC

jobvandervoort wrote: post #4

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.

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

#144

Post by lima » Fri, Aug 05, 2016, 2:22 PM UTC

cm3 wrote: post #93

lima wrote: post #23

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

If only phab didn't insist on squashing a patchset into a phabricator-commit, losing the carefully created history of a branch. Cumulative mega-patches are of little use when bisecting or trying to understand how a change works by being able to follow the steps to reach the final diff. A good commit history with separate commit messages explaining the diffs goes much further in allowing someone else to understand a c…

You can disable the squashing. It's a common complaint.

https://secure.phabricator.com/book/phabricator/article/arca...

> Phabricator could easily include their metadata in a merge commit

And this is what happens :-)

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

#145

Post by Nadya » Fri, Aug 05, 2016, 2:24 PM UTC

matthewmacleod wrote: post #112

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…

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.

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

#146

Post by Karunamon » Fri, Aug 05, 2016, 2:24 PM UTC

cloverich wrote: post #129

pille wrote: post #121

Earlier quoted context omitted.

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.

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).

Absurd being the key word. This isn't a simple misunderstanding we're talking about, it's a company employee using company time and resources (i.e. sanctioned by the larger company) for something that can charitably be described as misguided.

It raises questions about the internal company culture, their commitment to pragmatism (doubly important for a source code hosting site), and their priorities. Any developer could have told this person that a string match does not equal a linguistic match.

Small signals matter; they're usually all you get out of large orgs.

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

#147

Post by tetrep » Fri, Aug 05, 2016, 2:25 PM UTC

matthewmacleod wrote: post #112

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…

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 think it's reasonable if only so you can avoid the overhead of needing to deal woth censors. There's also a lot of overlap between open source and free speech, so I can understand a natural distaste for censorship in general.

To olay devil's advocate, what's wrong with offending people who read your source code? You can't harass people through source code in a meaningful way because you can't force them to look at the code through natural interaction with GitHub itself, if they see a project that is insulting, they can just ignore it.

It's not like a social media site where you can ensure your victims' feeds will be polluted with your insults.

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

#148

Post by lima » Fri, Aug 05, 2016, 2:25 PM UTC

Karunamon wrote: post #142

cookiesboxcar wrote: post #92

Earlier quoted context omitted.

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?

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.

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

#149

Post by mrmondo » Fri, Aug 05, 2016, 2:26 PM UTC

As I always say on every GitLab post on HN (and no I'm not paid to nor do I have any affiliation with the company) - we switched from a combination of Github + Gitolite/Gitosis to GitLab not long after it was release and my god it's damn good, It's really impressed us particularly in the last 12 months how rapidly they're developing the product and getting new released / fixed / features out. Especially like Gitlab CI w/ Docker.

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

#150

Post by UseStrict » Fri, Aug 05, 2016, 2:28 PM UTC

cloverich wrote: post #129

pille wrote: post #121

Earlier quoted context omitted.

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.

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).

When there are numerous alternatives to GitHub why would I continue to use them? Clearly they were not putting the time and effort in to both train their employee and review the content (simply reading the sentence would give context), why bother dealing with them?

Also why as a code hosting service would they be getting involved with the politics of the content of projects they host?