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

Gitlab 13.1

about.gitlab.com

Post reply on HN
Print view View original

51–60 of 90 posts

Re: Gitlab 13.1

#51

Post by thawkins »

dindresto wrote: post #4

With every release I wonder why our team is even paying for Gitlab Bronze. It seems to offer no value at all, might as well go for the free tier and save a thousand dollars a year.

Gitlab needs to be able to mix licenses on a single system, its current model requires all accounts in an org to operate at the same level, try selling a 1000 seat ultimate license at 99/user/month to tbe average sme. In all companies there are seats that need different levels of capabilities, gitlab is just way to expensive to use at anything above starter, the premium level works out at 2x more expensive than jira/bb/confluence with considerably less capability. I want to be able to buy 200 starter, 50 premium and 5 ultimate licenses and mix them on the same system.

Re: Gitlab 13.1

#52

Post by sytse »

threeseed wrote: post #22
sytse wrote: post #17

Earlier quoted context omitted.

This comment makes a lot of good points. I think we can stop recommending License and Contributors since GitLab is mostly used for closed source software. The templates will still be there but just not suggested until you started to create a new file. And you should be able to disable everything but the repo if you want to. And of course you can disable the repo as well if you just want the planning features for exam…

Also please put in place this simple UI rule: "If it doesn't need attention don't make it coloured or bold" e.g. thumbs up/down, report abuse etc.

Thanks for the examples.

BYW There is also a reply in this thread from a GitLab UX team-member who responds to a comment about the thumbs up/down and report abuse buttons https://news.ycombinator.com/item?id=23606854

Re: Gitlab 13.1

#53

Post by sytse »

threeseed wrote: post #47
jayd16 wrote: post #24

Earlier quoted context omitted.

>Graphic Design repo it emphasises Kubernetes, Packages and Security features that have zero relevance. And there is no way to disable them. You can do it in Settings > General > "Visibility, project features, permissions"

Not for everything you can't. I am using Gitlab Next and Kubernetes, Security & Compliance, Operations, Analytics, Members are not removable options.

Thanks, I will raise this with our product team.

Re: Gitlab 13.1

#55

Post by apple4ever »

thawkins wrote: post #51
dindresto wrote: post #4

With every release I wonder why our team is even paying for Gitlab Bronze. It seems to offer no value at all, might as well go for the free tier and save a thousand dollars a year.

Gitlab needs to be able to mix licenses on a single system, its current model requires all accounts in an org to operate at the same level, try selling a 1000 seat ultimate license at 99/user/month to tbe average sme. In all companies there are seats that need different levels of capabilities, gitlab is just way to expensive to use at anything above starter, the premium level works out at 2x more expensive than jira/…

They explicitly said they don't want to do that, for reasons that really aren't clear. There are a LOT of companies that want to be able to mix developers and reporters, but can't because the price is astronomical for zero benefit. So they live with a lower tier (likely free).

Doesn't make sense.

Re: Gitlab 13.1

#56

Post by maddyboo »

muratsu wrote: post #43
jtwaleson wrote: post #35

I somehow had a feeling Gitlab would be bought this year, but the list dramatically falls apart upon closer inspection: - Google: will never work, completely different mindset and engineering culture. Gitlab feels way too unrefined (in a good sense). - AWS: Gitlab is already too different from their tech, and will never be that tightly coupled with the rest of AWS. - IBM: :') they wish - MS: already has GitHub Any ot…

Being all-remote makes it harder to get acquired. Even if the acquirer is forward thinking, there are many complications to be addressed (compliance with existing hr/payroll/etc). Last I've checked Gitlab was en route to IPO which makes sense given their unique structure.

> Being all-remote makes it harder to get acquired

Do you think this has changed amid the pandemic, though?

Wouldn't having a proven remote workforce actually increase your desirability?

Re: Gitlab 13.1

#57

Post by sytse »

dan1234 wrote: post #33

Looks like WebAuthn is still missing, even though there seem to have been merge requests featuring it forever! Anyone know which milestone it’ll be merged into?

This relevant MR https://gitlab.com/gitlab-org/gitlab/-/merge_requests/26692 is scheduled (not guarateed) for 13.2 (July 22, 2020). Also see this issue https://gitlab.com/gitlab-org/gitlab/-/issues/22506

Re: Gitlab 13.1

#58

Post by josegonzalez »

sytse wrote: post #53
threeseed wrote: post #47

Earlier quoted context omitted.

Not for everything you can't. I am using Gitlab Next and Kubernetes, Security & Compliance, Operations, Analytics, Members are not removable options.

Thanks, I will raise this with our product team.

+1 At my last place, we deployed via Nomad and not Kubernetes, yet we had "AutoDevops" on every repository page and developers trying to use it/ask questions about it.

Being able to wholesale disable features across the install would be a good first step.

Re: Gitlab 13.1

#59

Post by igetspam »

stock_toaster wrote: post #37
jtwaleson wrote: post #35

I somehow had a feeling Gitlab would be bought this year, but the list dramatically falls apart upon closer inspection: - Google: will never work, completely different mindset and engineering culture. Gitlab feels way too unrefined (in a good sense). - AWS: Gitlab is already too different from their tech, and will never be that tightly coupled with the rest of AWS. - IBM: :') they wish - MS: already has GitHub Any ot…

> I think any giant company would have a hard time integrating all-remote Gitlab. Atlassian maybe? ( shudder )

I would stop using gitlab immediately if that happened.

Re: Gitlab 13.1

#60

Post by tenaciousDaniel »

threeseed wrote: post #11

It's great and impressive how quick Gitlab moves in adding new features. But if I have a Graphic Design repo it emphasises Kubernetes, Packages and Security features that have zero relevance. And there is no way to disable them. And that on every single repo it places these Add License/Contributors etc buttons front and centre even though for 99% of internal projects they serve no purpose. Every release Gitlab seriou…

A graphic design repo...that's fascinating. UI design? Print?

I've never seen designers use full-on version control, so this is super interesting to me. Do you consider yourself more of a technical person?

Post reply on HN