Live data from Hacker News

Moving to GitLab: Yes, it's worth it

about.gitlab.com

211–220 of 356 posts

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

#211

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

In this context? I'll agree that recede might be a better choice in this case, but as an undergrad in physics I hear the word retard being used in similar contexts all the time in the sense of slowing down. It crops up especially often in classical mechanics problems.

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

#212

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 seems like the action from the github employee was disproportionate. That sounds like a very risky environment to host your product on. The response seems to match the proportion of the action.

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

#213

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.

[deleted]

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

#214

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 also have xonotic on GitLab, it's quite awesome :)

Would love to hear your thoughts on developing a game using GitLab, anything we can improve in that regard?

[1]: https://gitlab.com/xonotic/xonotic

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

#215
post #121

Earlier quoted context omitted.

Maybe she actually could've read the text and figured it out herself before sending out the note? Just firing off a warning based on a simple text match seems high-handed and/or incompetent enough to consider leaving.

I actually assumed that this message was automated – "We found on objectionable word in your project, please don't use it." It just seems that this problems is remarkably easily solved with a simple "We are using a technical term correctly, maybe you should consider adjusting your automated emails." I do get the impression that people generally seem to be all to eager to take offence, and it strikes me as a bit ironi…

> I actually assumed that this message was automated – "We found on objectionable word in your project, please don't use it."

How is this any better?

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

#216
post #121

Earlier quoted context omitted.

Maybe she actually could've read the text and figured it out herself before sending out the note? Just firing off a warning based on a simple text match seems high-handed and/or incompetent enough to consider leaving.

Just to be clear, you're saying: "If large company x hires a single incompetent person, that is a good reason to never deal with said company again." I think that's the parents interpretation of OP and hence the "seems like a disproportionate response." (I agree it was absurd to flag the content).

People who represent themselves as employees of a company represent the company. If the company permits incompetent employees to behave like this on their work profiles, that's not an unreasonable deal-breaker.

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

#217
post #176

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.

For better or worse, the appearance of coming from a real person seems to be the trend in marketing automation. I think many people, especially outside of tech, believe they are interacting with a real person most or all of the time, when in reality, they only are during exceptions to common requests. But people like interacting with real people more than they like seeing "automated message blah blah".

Related: The company is slipping my mind right now, but one startup changed their email name in automated messages from male to female and saw improved metrics as a result.

https://en.wikipedia.org/wiki/Marketing_automation

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

#218
post #85

Earlier quoted context omitted.

They've done a lot of work on performance in the past year. I'd recommend taking it for another spin.

Not enough, apparently. That page takes 10.5s to load and fails several performance metrics. https://tools.pingdom.com/#!/cOKg2F/https://gitlab.com/gitla...

I get 5.5s now when I re-run it (probably due to caching). We've been working incredibly hard to make it faster, we have to use it everyday, so we know exactly how annoying the lack of speed can be.

For example, take a look at the drop in response time in the middle of last month: http://stats.pingdom.com/81vpf8jyr1h9/1902794/2016/07

We've focused on speeding up some more common pages (Issues, MRs, etc.), but still a ways to go for the rest of the application!

Ceph should make a big difference once we get GitLab.com running on it in a few months, the reason the commits page specifically is so slow is because our current infrastructure is bottlenecked by filesystem-heavy interactions (e.g. getting all the recent git commits for a repository).

Ceph issues are here: https://gitlab.com/gitlab-com/infrastructure/issues?scope=al...

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

#219

Earlier quoted context omitted.

That's some great feedback, thanks! Any feature requests for Issues? If you plan on doing physical events, drop me an email (job at gitlab).

Feature requests for Issues: priorities, and states other than open and closed. These are the biggest things keeping us from using GitLab issues rather than an external tool. We need to be able to set priorities (ideally customizable, but at minimum high/med/low). We can kind of do that through labels, but it's messy because you can only search for one label at a time (no boolean combinations of labels). Right now, w…

Actually you can add priorities to labels :) http://docs.gitlab.com/ce/user/project/labels.html#prioritiz... You can also search for several labels in the current release. Just select some in the dropdown :)

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

#220

Earlier quoted context omitted.

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.

GitHub had tabs at the top, redesigned to use a sidebar, then went back to tabs at the top, I believe.
Post reply on HN