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

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

#191

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

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 fine to use a different site for a project.

It cannot be healthy to have all our eggs in one basket (Github), regardless of how featureful and nice Github is, especially so given the availability of viable options. To that end, we should not complain when a project, say, evil-mode is on bitbucket, and similarly not ask a project to open shop on github.

I mean, if we don't work towards a fully distributed project model ala fossil-scm (via things like git-appraise), we should at least use alternatives when we can, and not strengthen Github's monopoly.

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

#192

Post by kuschku » Fri, Aug 05, 2016, 3:24 PM UTC

olejorgenb wrote: post #163

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

Interestingly, some of those features were introduced by gogs first, and then appeared at GitHub - like the tabs on top.

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

#193

Post by zcdziura » Fri, Aug 05, 2016, 3:24 PM UTC

dijit wrote: post #162

Zecc wrote: post #114

Earlier quoted context omitted.

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.

Many large (or aspiring) open-source projects seek to create a community of users around it, and having a lower barrier of entry to create such a community only helps the project. As you've said, GitHub provides such a low barrier.

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

#194

Post by Singletoned » Fri, Aug 05, 2016, 3:25 PM UTC

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'm tempted to have a play with this, and see how many legitmate, non-offensive uses of "retard" I can get into my repos.

EG The french for "I'm late" is "Je suis en retard".

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

#195

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

Looks like a very big sign that more warnings will come later, and you'll have to spend time fighting such things now, and start worrying about your data be cut from the site without previous notice.

Going away is the correct response, fighting the decision is never useful. One might wait a bit to see if it's a fluke, but that will certainly depend on the GP's evaluation of the company.

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

#196

Post by WayneBro » Fri, Aug 05, 2016, 3:29 PM UTC

favadi wrote: post #164

scaryclam wrote: post #156

Earlier quoted context omitted.

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?

If he says yes, are you going to fail to acknowledge that your complaint was satisfied and then move the goal posts again?

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

#197

Post by explorigin » Fri, Aug 05, 2016, 3:35 PM UTC

pille wrote: post #176

tedmiston wrote: post #167

Earlier quoted context omitted.

Presumably it was an automated message.

Someone had to design that automation. And it sounds like the message was at least made to look like it came from a person.

Go read up on Github user: CoralineAda [1][2] Then consider that GitHub hired her. I would not be surprised if the this automated script and her employment were directly related.

[1] https://github.com/opal/opal/issues/954 [2] https://github.com/CoralineAda?tab=activity

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

#198

Post by GFK_of_xmaspast » Fri, Aug 05, 2016, 3:35 PM UTC

favadi wrote: post #173

allemagne wrote: post #161

Earlier quoted context omitted.

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?

I'm in an asian country where racist is (mostly) not a thing, so why people cares about those rates is a mystery for me. In my thought, if there are 2 candidates for a leader role, and they decided "oh, we need more women in leader rank, we should chose her", it is just wrong. Race/gender shouldn't be even considered as a factor in those situations.

Which asian country is that, because I'm not immediately thinking of too many that fit that bill.

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

#199

Post by senthil_rajasek » Fri, Aug 05, 2016, 3:37 PM UTC

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

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

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

#200

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

jobvandervoort wrote: post #20

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.

That's great to hear. Would love to hear your feedback.

Sure! The only reason I wasn't using GitLab before is that I had a writer working remotely on my game and I didn't know how to explain to her how to use it. So I had moved everything to GitHub and told her to use their desktop app, which makes the clone/commit/push/pull flow amazingly simple.