Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Moving to GitLab: Yes, it's worth it

about.gitlab.com

Post reply on HN
Print view View original

241–250 of 356 posts

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

#241

Post by rdtsc »

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.

Maybe if they had some allegiance to or belief in Github fixing the issue, talking to employee, retraining them, it might be worth. But when there is another project that is just as easy to use, it often just easier to drop it and switch.

Also that interaction with Github, can be interpreted as a pointer to larger systemic issue (for better or for worse) which the customer doesn't believe will be solved with a simple email.

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

#242

Post by analogmemory »

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

I was pretty impressed how easy it was for me (a server newb) to setup my own GitLab CI on a AWS server. For my projects now it takes around 15 seconds from when I push to GitLab for it to be deployed.

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

#243

Post by efvxcgci »

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.

It's quite disappointing to see people defending a company that hires bigoted political activists to crawl users' projects in order to harass users for perceived political transgressions.

And what level of access do these on-staff political activists have to private user information? What measures, if any, does GitHub have in place to prevent one of their political activist employees from using privileged information to go after perceived political enemies or even just retaliate against users who protest being harassed?

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

#244

Post by tauriedavis »

microcolonel wrote: post #33
jobvandervoort wrote: post #4

As always, we're happy to answer any questions about GitLab.

I feel as though some of the recent UI changes were cosmetic and degraded the experience. I was especially unhappy about the sidebar being pushed into a hamburger menu (which can be pinned open, mind you). I'd really like for UI updates in the future not to be jarring and seemingly pointless. I really liked the UI right before the overhaul, only minor tweaks seemed truly necessary. Many of the tweaks I would have sug…

Thanks for your feedback - we are always working on improving the UX/UI and appreciate your input! I know that large changes can feel jarring at first but we hope that in the end, they help improve workflow and productivity.

The sidebar is a global navigation and not always necessary when interacting with page-specific content on the site. GitLab is very content heavy and by allowing the sidebar to be collapsed, it allows users to have more space on smaller screens to read/scan the information that they need. As you mentioned, the sidebar can be pinned so users can view the navigation all the time if they prefer, esp if they are using a larger screen.

If you have other examples of changes that you felt were pointless, I'd love to find out the reason for the change for you!

I also urge you to voice your opinion by making an issue for changes that you think would help improve the user experience. https://gitlab.com/gitlab-org/gitlab-ce/issues/new

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

#245

Post by zwerdlds »

kmonsen wrote: post #239
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…

Why are you specifying it was a woman?

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

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

#246

Post by zegerjan »

jobvandervoort wrote: post #25
insanebits wrote: post #6

I'm recently setup Gitlab for my personal projects, import from bitbucket was a breeze. I've used omnibus installer and it was almost painless, only a couple of issues because of LXC limits. My only concern is resource usage, it does take at least 2Gb memory, are there any options to tweak it?

We do recommend you allocate resources generously, with 2Gb minimum. That said, there are ways to tweak it. I believe you can reduce the default amount of Unicorn workers to one, as a start. Further than that I'm out of my league; I'll ask one of our awesome service engineers to respond here.

Also, please lower the default number of unicorn workers from 3 to 2.

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

#247

Post by moby »

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.

Have you tried using GitHub Importer for any projects?

https://github.com/new/import

Let me know how it works for you; happy to provide feedback to make it easier for your purposes!

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

#249

Post by iamdave »

senthil_rajasek wrote: post #238
gknoy wrote: 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.

That's offensive to people with receding hairlines.

Turnabout's a bitch, ain't it?

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

#250

Post by zo1 »

squeaky-clean wrote: post #186
pille wrote: 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.

Then apply the above-mentioned logic to the person/company that endorsed/approved said automated script.
Post reply on HN