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

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

#301

Post by iamdave » Fri, Aug 05, 2016, 7:34 PM UTC

jobvandervoort wrote: post #66

sdesol wrote: post #35

Earlier quoted context omitted.

Since I have your attention, something else that I think should be on your radar is creating/defining supported injection points in GitLab's UI. If you haven't done so, you should look at what Microsoft has done with Visual Studio Team Services. By providing supported injection points in GitLab's UI, GitLab will be able to signal to others, that they are a solution you can safely build on top of.

That's a very interesting idea. Right now, to integrate deeply, you'd have to go through the heavy-handed process of creating a service [0]. That then does allow you to do almost anything, but the barrier to entry for that is high. I created an issue for your proposal and hope you can provide some more feedback on how this would work, ideally [1]. [0]: http://docs.gitlab.com/ce/project_services/project_services.... S…

I'm constantly impressed by how involved GitLab engineers are not just on HN but other communities when brought up. Not sure if you guys have people constantly looking for mention of "GitLab" but even if you are, the responsiveness and agreeableness to look into issues and invite people to be a part of the solution they seek out are phenomenal habits and I applaud you guys for it. It's one of the many reasons I converted a while back from Github and probably wont be looking back anytime soon.

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

#302

Post by mildbow » Fri, Aug 05, 2016, 7:34 PM UTC

j_s wrote: post #289

GFK_of_xmaspast wrote: post #198

Earlier quoted context omitted.

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

I've heard citizens from Singapore make this claim.

Singapore, purportedly, is racist against Indians.

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

#303

Post by senthil_rajasek » Fri, Aug 05, 2016, 7:36 PM UTC

mildbow wrote: post #295

senthil_rajasek wrote: post #272

Earlier quoted context omitted.

A good writer has the responsibility of choosing the correct word. That's what makes them good. I apologize if my use of some words offended you. My reasoning is that words that trigger specific memories and experiences in a person are more hurtful. The world is not a perfect place but it is constantly changing and evolving. I keep working hard to use words that are not hurtful.

Sure. But a good writer does not mean an inoffensive one. If pressed, I would even argue that the opposite is that case. You are so off the mark that you must be trolling or "receded".

Being offensive is certainly a choice but not on this forum if I remember the rules correctly.

I am not trolling, I am merely saying that a good writer should take responsibility for his choice of words.

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

#304

Post by SamReidHughes » Fri, Aug 05, 2016, 7:39 PM UTC

WayneBro wrote: post #196

favadi wrote: post #164

Earlier quoted context omitted.

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?

That's an essential code review feature.

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

#305

Post by EugeneOZ » Fri, Aug 05, 2016, 7:52 PM UTC

Their UI is too slow (as many other Ruby web apps).

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

#306

Post by auntienomen » Fri, Aug 05, 2016, 8:02 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 the correct terminology in signal processing and has been since the 19th century. You are getting downvoted because you sound as ignorant as the politician who objected to funding research in Lie Theory.

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

#307

Post by __david__ » Fri, Aug 05, 2016, 8:09 PM UTC

0x0 wrote: post #151

bovermyer wrote: post #107

Earlier quoted context omitted.

I had the same experience. The other thing I would add is that the social side of Gitlab is not as refined as GitHub's. There's no "timeline," for example. I pay for GitHub and enjoy it.

On the other hand, gitlab's "network" view of commit branches is excellent and I've never been able to find anything remotely similar on Github. Essential to manage development in multiple concurrent branches.

Isn't that just gitk[1] or tig[2] (my favorite)?

[1] comes with git, screenshot: http://static.lwn.net/images/ns/kernel/gitk.png

[2] http://jonas.nitro.dk/tig/

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

#308

Post by 0x0 » Fri, Aug 05, 2016, 8:13 PM UTC

__david__ wrote: post #307

0x0 wrote: post #151

Earlier quoted context omitted.

On the other hand, gitlab's "network" view of commit branches is excellent and I've never been able to find anything remotely similar on Github. Essential to manage development in multiple concurrent branches.

Isn't that just gitk[1] or tig[2] (my favorite)? [1] comes with git, screenshot: http://static.lwn.net/images/ns/kernel/gitk.png [2] http://jonas.nitro.dk/tig/

It's similar, but gitlab's graph has a much more readable and sensible 2d layout. The way tig and gitk line up/layout the branches is often very confusing. Gitlab makes it much clearer where the branch lines go, while tig/gitk seem to left-align everything as much as possible, making the lines twist and turn and difficult to trace.

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

#309

Post by SatvikBeri » Fri, Aug 05, 2016, 8:14 PM UTC

OliverJones wrote: post #9

Working for a 15-year old small software company, I converted a whole bunch of ancient CVS stuff (yeah, yeah, don't laugh unless you also have 15 years of profitability) to GitLab CE. After a couple of false starts it went flawlessly and now works flawlessly. (I used the tigris.org migration tools). The GitLab team is doing a great job. Thanks you guys.

One of the most successful companies I worked at had no version control or unit tests whatsoever. The code was all maintained by one person (the company relied heavily on custom software internally but it wasn't their product), who was able to keep the codebase small enough to basically hold in his head the whole time despite generating millions of dollars of value.

That's certainly not how I would write code today, but it is amazing to see how much top-notch programmers vary.

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

#310

Post by lewisl9029 » Fri, Aug 05, 2016, 8:41 PM UTC

atomi wrote: post #286

jobvandervoort wrote: post #75

Earlier quoted context omitted.

We recommend Gogs for people that want to run on machines with little memory, it's great.

Yeah it runs great on an rPi. I doubt you can say that about Gitlab or RhodeCode.

I wish GitLab could be a bit lighter weight as well. I'd love to spin up the cheapest VM instance I can find on a cloud provider, pull a Docker container, and have a working GitLab instance up and running, but they "strongly advise against" running GitLab at the amount of memory those cheap VMs usually come with (usually around 512MB) [1].

[1] https://github.com/gitlabhq/gitlabhq/blob/master/doc/install...