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

81–90 of 90 posts

Re: Gitlab 13.1

#81

Post by christina_hupy »

ldoughty wrote: post #67
sytse wrote: post #23

Earlier quoted context omitted.

"Somewhere in comments here will be reply from Gitlab employee, saying that dogfooding is something they are constantly working on" To ensure we meet your expectations I want to state that we're continuously working on dogfooding, you can track our progress in https://gitlab.com/gitlab-org/gitlab/-/issues?label_name=Dog... "What they should be doing is to update documentation pages with feature maturity level and hav…

While not the above commenter, I found the reply enjoyable. Thank you. GitLab had been great for us, though we've had issues around their educational institutions license.. so we can't use a lot of the fancy features... But I've enjoyed ops work more on GitLab than GitHub or Jenkins.

Great to hear you are enjoying GitLab and we value you as an Education Program member. We'd love to hear your constructive feedback on any issue's you've had. In the GitLab spirit, we started the Education Program as a MVProgram and are working hard to mature it. We have an open epic - please feel free to provide input. https://gitlab.com/groups/gitlab-com/marketing/community-rel...

Re: Gitlab 13.1

#82

Post by xhl »

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/…

@thawkins Thank you so much for your inputs on our pricing model!

Our current model do not have multiple plans for one customer https://about.gitlab.com/handbook/ceo/pricing/#multiple-plan... as @apple4ever mentioned.

However, it's extremely important for us to hear from you. We recently clarified our Pricing Philosophy and Collaboration on pricing with you is part of it: https://about.gitlab.com/handbook/ceo/pricing/#pricing-philo...

We definitely take your inputs back and consider to build into our next iteration on the pricing strategy.

Re: Gitlab 13.1

#83

Post by xhl »

apple4ever wrote: post #55
thawkins wrote: post #51

Earlier quoted context omitted.

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.

@apple4ever Thank you very much for your feedback! This is very helpful for us to iterate on our handbook explanation and our pricing strategy.

Re: Gitlab 13.1

#84

Post by [deleted] »

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/…

[deleted]

Re: Gitlab 13.1

#85

Post by efiecho »

samdbeckham wrote: post #74
efiecho wrote: post #69

Earlier quoted context omitted.

> Better UI than GitHub I think that GitHub has a much better UI than GitLab. GitLab is slow and bloated compared to GitHub. Requiring Javascript for browsing the code repository is just bad design.

GitLab employee here. As much as it pains me, I have to agree with you for the most part. Performance is one of the biggest pain points for our frontend team, but is something we're actively working on. Here's one of our epics to show our progress: https://gitlab.com/groups/gitlab-org/-/epics/716 We're in the process of migrating parts of our codebase from haml templates to Vue apps, which does have the unfortunate d…

Well, that's interesting information. I believe it when I see it, but it could be that my criticism of GitLab is no longer valid at some point in the future.

Re: Gitlab 13.1

#86

Post by nuritzi »

kabacha wrote: post #66
rossmohax wrote: post #20

Earlier quoted context omitted.

> It's great and impressive how quick Gitlab moves in adding new features. Don't trust their feature list, they often "forget" to use it themselves. Many of those features are there to tick the box and daze executives, but are barely usable in practice. It took them a year to start supporting Kubernetes clusters with RBAC, they didn't use autodevops for their own releases, even for simple components, nor any kubernet…

I feel a bit the opposite. I've been totally spoiled by gitlab to the point where contributing to libre github projects has started becoming difficult. We use gitlab at work and it has been great, though we have really great sysadmins so maybe my perception is a bit skewed. That being said Gitlab's UI is still commits a lot of UI complications that makes it inferior to github for managing libre projects. I really wis…

GitHub is an established player in the technology space and has done a really great job at fostering its open source community.

You're right that GitLab is trying to differentiate itself as the best place to scale software, and so it feels like its focus is on enterprises. That's where the open source strategy also currently aligns. GitLab is making the best platform to help open source projects thrive at scale.

I'm the new Sr. Open Source Program Manager at GitLab and was recently hired to build out our GitLab for Open Source program (https://about.gitlab.com/solutions/open-source/). This program allows open source projects to use GitLab's top tiers for free, and it provides assistance to large open source organizations throughout their migrations. We are providing open source projects with GitLab’s top-of-the-line features, that enterprises are using, to help them along their own journey.

As I mentioned, GitHub is doing a lot of great things, and I think that GitLab used to be perceived as merely playing a game of catch up. This is no longer where we are today. We're fast at iterating on our product and are blazing ahead on creating a platform that enables cross-functional team collaboration, and industry-standard features for the full software development lifecycle. We're working on a similar strategy with our open source offering -- so that we're not playing catch up, but are instead defining a new standard.

As an open-core company, we have an open roadmap for our product and for everything else we do. If you have ideas for our community relations team (I'm part of this team), we welcome your feedback! You can reach us via our forum: forum.gitlab.com, and via community@gitlab.com. You can also read all about what we do and how we work here: https://about.gitlab.com/handbook/marketing/community-relati...

Re: Gitlab 13.1

#87

Post by cdybenko »

elmolino89 wrote: post #73

Version control for GitLab wiki is still not there. Supposedly it will be in 13.2. For a small shop using GitLab local install versioning of the systems/software/lab protocols documentation is something hard to live without.

Hey GitLab Wiki PM here!

We do have an issue scheduled in 13.2 for Wiki diffing. However this still won't allow you to revert a change but will visually help you see the diffs line by line (just like in MRs):

https://gitlab.com/gitlab-org/gitlab/-/issues/15242

(FYI that issue is a community contribution so I can't guarantee it will ship in 13.2, but we'll try!)

I'm sure you're aware, we also have git versions of the wiki in the UI: https://docs.gitlab.com/ee/user/project/wiki/#viewing-the-hi...

Can you tell me more about your use case for versioning?

Re: Gitlab 13.1

#88

Post by sam-white »

rossmohax wrote: post #20
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…

> It's great and impressive how quick Gitlab moves in adding new features. Don't trust their feature list, they often "forget" to use it themselves. Many of those features are there to tick the box and daze executives, but are barely usable in practice. It took them a year to start supporting Kubernetes clusters with RBAC, they didn't use autodevops for their own releases, even for simple components, nor any kubernet…

> Who in the right mind is going to enable Web Application Firewall feature, when rules exceptions cannot be configured?

Currently we are using ModSecurity for our Web Application Firewall and rather than duplicating their documentation, we refer our users to ModSecurity's documentation for rule configuration. Rule exceptions with GitLab's WAF are possible as documented on the ModSecurity website: https://www.modsecurity.org/CRS/Documentation/exceptions.htm...

It is also worth noting that we are in the process of designing a more refined, UI-based policy management experience. While this policy management experience is starting with support for Cilium Network Policies only, we plan to eventually add support for WAF rules as well. We would love to get input or feedback you have on the direction we are headed with our policy management interface at https://gitlab.com/groups/gitlab-org/-/epics/3403

Re: Gitlab 13.1

#89

Post by JetSpiegel »

indigochill wrote: post #50
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 actually have no idea, but isn't "open core" a turn-off to would-be acquirers as well, since the core can fork out from under them if they try to work too hard against the wishes of the community? Maybe there have been open core acquisitions. I don't follow startup news that closely.

Who would maintain the fork?

Re: Gitlab 13.1

#90

Post by elmolino89 »

cdybenko wrote: post #87
elmolino89 wrote: post #73

Version control for GitLab wiki is still not there. Supposedly it will be in 13.2. For a small shop using GitLab local install versioning of the systems/software/lab protocols documentation is something hard to live without.

Hey GitLab Wiki PM here! We do have an issue scheduled in 13.2 for Wiki diffing. However this still won't allow you to revert a change but will visually help you see the diffs line by line (just like in MRs): https://gitlab.com/gitlab-org/gitlab/-/issues/15242 (FYI that issue is a community contribution so I can't guarantee it will ship in 13.2, but we'll try!) I'm sure you're aware, we also have git versions of the…

Sorry for the late reply.

Few features (apart from be able to view wiki diffs) from my point of view:

1. Wiki edits in activity

2. User wiki edit history (= edits times, pages, size of diffs)

Maybe in a long run it will be good to have Markdown based collaborative document editing. Meaning that each editor can branch the draft doc, introduce changes. Then these branches will need to be reviewed and merged, probably by 1-2 people.

Hope it helps

Post reply on HN