Live data from Hacker News

Moving to GitLab: Yes, it's worth it

about.gitlab.com

251–260 of 356 posts

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

#251
post #236

Earlier quoted context omitted.

It's a completely different word, though. "retard" (pronounced "RE-tard") is the derogatory term, but the context used in this sentence (to slow something down) is pronounced "re-TARD". The only people who would be offended by that are those who have never been introduced to the other word with the same spelling (but different sound). Indeed, the _primary_ listed meaning for this word [0] is the verb form, not the de…

recede is less ambiguous.

Is it? What else could retard mean in this context?

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

#252

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

We're working hard on making CI super easy to use and setup. If you want to give it a spin, check out our recent blog post on starting from 0: https://about.gitlab.com/2016/07/29/the-basics-of-gitlab-ci/

Im using Jenkins right now to basically handle docker deployments. Without taking the time to actually read up on it in depth, does GitLab CI handle ways for me to essentially just pull prebuilt images and run them on a targeted server with desired settings? I'm already preparing to move to GitLab CI for images that I build myself (since Im already storing the Dockerfiles on gitlab)

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

#253

Earlier quoted context omitted.

recede is less ambiguous.

That's offensive to people with receding hairlines. Turnabout's a bitch, ain't it?

In popular American usage recede is not associated with hairline. People with receding hairline are not marginalized by society.

Now "bitch" that's offensive.

Edit: spell correct.

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

#254
post #148

Earlier quoted context omitted.

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

Gitlab is unfortunately a pig, in the large and bloated sense of the term. Which is really sad! I love the app, it looks better than Phabricator and does so much more, but then I can throw Phabricator on the same droplet I use for plenty of other stuff with resources to spare for $5/month, where Gitlab would require a dedicated $10 instance just due to memory usage alone. Guess I'm just not the target audience :(

You can use gitlab.com for free... don't need to install it in your own box.

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

#255

Earlier quoted context omitted.

Wow, that is absurd. Did you ever follow up with the employee who sent you a note? What did flagging entail? I.e., were you not able to use the repo?

Yes. She indicated that it doesn't matter how the word is used, some will see it as aggressive. As she appeared to be a non-technical person mysteriously employed by GitHub as some consolation to some organization (IIRC it was called the "Ada Initiative") I realized that github is no longer a technology company. It's a Social Justice company. Good luck to them--I don't even disagree with the basic premise--but I like…

Some of the commenters here assumed that the message was automated, you're making it abundantly clear thats was not the case. In fact she defended her position. Did you try to escalate it? This is absurd.

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

#257

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 did the same with my business, personal projects, and open source stuff I worked on.

Github is never getting another penny from me.

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

#258

Earlier quoted context omitted.

That's offensive to people with receding hairlines. Turnabout's a bitch, ain't it?

In popular American usage recede is not associated with hairline. People with receding hairline are not marginalized by society. Now "bitch" that's offensive. Edit: spell correct.

Words have meaning. Words have power. This much is not in debate, as far as I'm concerned (so far). Where I have to take pause is taking one usage (however derogatory) of a word and applying to every meaning and usage regardless of what the context actually is as some manifestation of virtue signalling. At this point we may as well throw out language, diction and rhetoric entirely as any word and phrase can be twisted to be offensive even when a word is used entirely and wholly in accurate and proper context.

People with receding hairline are not marginalized by society

You're obviously not aware with how common male baldness jokes are in sitcoms and entertainment, are you? I encourage you watch a few episodes of Seinfeld to see how much influence hair and baldness has on men and their self esteem in the dating world.

They might not be marginalized, but then again I guess it depends on how one is using the word 'marginalized' to begin with, which brings us back to square one: turnabout is a bitch.

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

#259
post #153

Earlier quoted context omitted.

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.

The point is the same though. Resting a project's livelihood on a company that employed obviously incompetent process/humans/scripts is a risky move, and removing that livelihood from that company makes total sense.

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

#260

Earlier quoted context omitted.

Why are you specifying it was a woman?

Moreover, why would he even know in the first place?

Perhaps she signed-off her email/post/comment with a female name? You know, it is perfectly reasonable to assume gender when the name is obvious. E.g. the odds of a person called "Samantha" being male are miniscule compared to it being a female. Because in both cases, "it" is a person we are talking about.

We can't just erase gender. People think in gender, and they consequently speak it. I don't think twice about mentioning "some guy" commented on my post, for example. Just the other day I decided to be even and refer to a hypothetical person by using "s/he", and even got called out on it.

Post reply on HN