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

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

#121

Post by pille » Fri, Aug 05, 2016, 1:54 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.

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.

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

#122

Post by akerro » Fri, Aug 05, 2016, 1:54 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.

We moved from GitHub to GitLab CE at our company and co-workers started using GitLab.com for their personal projects, moved away from github.

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

#123

Post by Chris2048 » Fri, Aug 05, 2016, 1:55 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…

What did the email say?

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

#124

Post by danielrmay » Fri, Aug 05, 2016, 1:55 PM UTC

matthewmacleod wrote: post #118

GitLab is great and it's lovely to see a diverse selection of tools, but I'm not too convinced of the cost benefits – for a team with 100 developers, the annual cost of ~$11,000 is a pretty small amount compared to the maybe $25m salaries you'll be paying!

Avg salary of $250k per dev? Are you hiring?

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

#125

Post by akerro » Fri, Aug 05, 2016, 1:55 PM UTC

matthewmacleod wrote: post #118

GitLab is great and it's lovely to see a diverse selection of tools, but I'm not too convinced of the cost benefits – for a team with 100 developers, the annual cost of ~$11,000 is a pretty small amount compared to the maybe $25m salaries you'll be paying!

Could you take a look at price for GitHub for same big team please?

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

#126

Post by throwanem » Fri, Aug 05, 2016, 1:57 PM UTC

jobvandervoort wrote: post #95

thinkMOAR wrote: post #86

I would like to see that there is just one gitlab version, and that the enterprise features are simply available in the community edition too. I will not pay just for a feature like repo mirroring, but it's i think a feature many people will use and or utilise when moving, migrating to a gitlab setup. But it is the one and only feature i am missing so not worth upgrading to EE for me. As soon as an alternative (open…

We do our best to make CE and EE excellent, where the features that land in EE are mostly interesting for larger teams. For every feature that we don't bring to CE, this is always a hard decision. We wrote about this here: https://about.gitlab.com/2016/01/11/being-a-good-open-source...

I'd love to see an a la carte licensing option, where an organization could start with stock CE and license just the features they need. I realize that'd be a bear to implement, though.

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

#127

Post by oDot » Fri, Aug 05, 2016, 2:01 PM UTC

jobvandervoort wrote: post #74

oDot wrote: post #70

I'm working on a proper Docker setup for GitLab development which I think can be made production-ready pretty easily after the development version works. It's hard separating the different moving parts (gitlab, gitlab-workhorse, gitlab-shell+ssh, postgres/mysql, redis) but I think I will have a merge request ready soon enough :D

Wow, this sounds great! Do you have anything to share? Do you leverage GDK? [0] [0]: https://gitlab.com/gitlab-org/gitlab-development-kit

Not right now. I'm following the install from source guide so it'll be as close as possible to production. I'll change some things the omnibus package does better, then apply the GDK stuff so people could use it for development.

I have some code. I guess I can submit a merge request + issue on gitlab-ce and gitlab-workhorse, but I need to read CONTRIBUTING and PROCESS first :P

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

#128

Post by cdawzrd » Fri, Aug 05, 2016, 2:04 PM UTC

jobvandervoort wrote: post #84

atsaloli wrote: post #79

I love how responsive our local (departmental) instance of GitLab CE is -- it's downright snappy compared to the corporate instance of JIRA. We love the issue tracking subsystem of GitLab and use it as our main ticketing system. We've done a few talks on Git basics to help increase adoption, and are doing a free webinar "Git Foundations: Basic Concepts and Definitions" next week: https://www.eventbrite.com/e/git-foun…

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, when you assign an issue to a user, it's considered "in progress", and from there it can either be unassigned or closed. It would be nice to separate the state of the issue from the assigned user, since in our current workflow we assign many issues to a user, but that user might only be working on a few of them at a time. Using our current bug tracker, we can differentiate between "Open, unassigned", "Open, assigned", "Open, in progress", "Fixed", "Verified", "Closed", etc. I know having a completely customizable state diagram for issues is a big software task, but maybe there is some intermediary level of complexity that would allow better tracking of what is actually being worked on now vs. what is assigned to people.

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

#129

Post by cloverich » Fri, Aug 05, 2016, 2:06 PM UTC

pille wrote: post #121

matthewmacleod wrote: post #112

Earlier quoted context omitted.

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

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

#130

Post by LeifCarrotson » Fri, Aug 05, 2016, 2:06 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.

Perhaps to a comment from a random user, this would be disproportionate. But when it is a GitHub employee sending these messages, someone needs to communicate the issue to them in metrics they will understand, like projects leaving.