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

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

#201

Post by assface » Fri, Aug 05, 2016, 3:43 PM UTC

senthil_rajasek wrote: post #199

"Phase shift varies with frequency and can advance or retard as the frequency changes" I looked up Webster's American English Thesaurus and the antonym for 'advance' in the sense that it's used in your sentence is recede. Here is the same sentence rewritten using recede. "Phase shift varies with frequency and can advance or recede as the frequency changes." This is an easy case where you could have used correct langu…

> If you would like to know why it's offensive to some people, I could educate you.

Please do.

https://i.imgur.com/jElyDnl.jpg

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

#202

Post by hudell » Fri, Aug 05, 2016, 3:44 PM UTC

kh_hk wrote: post #58

hudell wrote: post #18

I recently moved my personal project from GitHub to GitLab and the whole process took me less than a minute, with a simple git remote set-url on the client side. The future is amazing.

Not wanting to diminish what GitLab is doing, but what you mention is an inherent characteristic of git itself that applies the same way to GitHub, Bitbucket and a self hosted git bare repository. Any git host should expose a git interface for it to work as a git repository.

Yes, but they simplified it a lot. I just connected to github, chose the repository and clicked import. Maybe all of those services have it that way, but I'm just glad that GitLab had it.

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

#203

Post by Lawtonfogle » Fri, Aug 05, 2016, 3:44 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.

Given no other information I would agree. But given other information both about Github and about the kind of processes that seek you out to tell you that you are being offensive, I understand. Maybe this was a one time thing, maybe it will be another donglegate. If it is easy enough to move, why wait and find out?

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

#204

Post by Tobold » Fri, Aug 05, 2016, 3:47 PM UTC

technomancy wrote: post #45

I was pretty impressed with how easy it was to get free CI runs on pushes and merge requests with my OSS game: https://gitlab.com/technomancy/bussard/commit/73e84d11ed33ff...

Very interesting! I remember trying your game a few months back, but I didn't have the time to really get into it.

I was thinking about making a game in Löve for a while now, but I have never done any automated testing with it.

Is there a good tutorial for that? Or do you feel like writing one? ;)

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

#205

Post by kh_hk » Fri, Aug 05, 2016, 3:48 PM UTC

hudell wrote: post #202

kh_hk wrote: post #58

Earlier quoted context omitted.

Not wanting to diminish what GitLab is doing, but what you mention is an inherent characteristic of git itself that applies the same way to GitHub, Bitbucket and a self hosted git bare repository. Any git host should expose a git interface for it to work as a git repository.

Yes, but they simplified it a lot. I just connected to github, chose the repository and clicked import. Maybe all of those services have it that way, but I'm just glad that GitLab had it.

That is a different case than configuring a different remote on config and pushing to another host which is what I interpreted reading your comment, my bad.

Out of curiosity, does the import process include all issues, PR and comments?

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

#206

Post by matt4077 » Fri, Aug 05, 2016, 3:51 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?

First of all, there is the moral case: Certain groups have been kept away from positions of power & wealth to such an extend that taking remedial action is warranted.

Secondly: there are obviously some differences in the behavior, knowledge, and culture of different groups and it is beneficial for a company to include those and profit from it.

But... you can't have gone through more than 14 years of life without having heard all thread a few times, can you?

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

#207

Post by Nadya » Fri, Aug 05, 2016, 3:51 PM UTC

matthewmacleod wrote: post #187

Nadya wrote: post #145

Earlier quoted context omitted.

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…

>It's also perfectly legitimate for you to say "I don't want to do that".

At which point you get harassed by a mob, spammed with issues that clutter up your project, and get emailed death threats.

Github is allowed, of course, to choose which projects they decide to host. Demanding the removal of the word "retards" [0] or a project would be shut down drove at least one developer away.

So no - that isn't "perfectly legitimate" for that community. "I don't want to do that" is not good enough.

[0] https://github.com/nixxquality/WebMConverter/commit/9fde8f33...

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

#208

Post by justinpombrio » Fri, Aug 05, 2016, 3:51 PM UTC

senthil_rajasek wrote: post #199

"Phase shift varies with frequency and can advance or retard as the frequency changes" I looked up Webster's American English Thesaurus and the antonym for 'advance' in the sense that it's used in your sentence is recede. Here is the same sentence rewritten using recede. "Phase shift varies with frequency and can advance or recede as the frequency changes." This is an easy case where you could have used correct langu…

"retard" is also a correct word to use here; it means "to delay".

> If you would like to know why it's offensive to some people, I could educate you.

Could you educate us as to why it's offensive in this context? I think we all know why calling a mentally handicapped person "retarded" offends some people, but no one did so.

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

#209

Post by matt4077 » Fri, Aug 05, 2016, 3:54 PM UTC

I tried their free tier and it was just extremely slow. A small project where commits usually took 5 seconds now needed >1min for any operation.

Moved it all into the google cloud and it works at the speed of the network. But we don't really need any of the features except the git repository anyway.

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

#210

Post by caseysoftware » Fri, Aug 05, 2016, 3:55 PM UTC

cm3 wrote: post #191

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.

Assuming Github's ToS applied here, it's unlikely that the project owners would have succeeded in keeping the content as is on github by arguing for it. This is regardless of the legitimacy of the content. Being on Github isn't critical for every project, and we need more projects that have their primary location on Bitbucket, Gitlab, etc. instead, in order to break the Github monopoly by making it normal that it's f…

Github does have the lead in terms of exposure and discoverability. To take advantage of that, I've left placeholders in all my projects that are elsewhere now: https://github.com/caseysoftware/marvel-php

If you find it on Github, you can find out how to get started but everything else is on Gitlab.