Maturity
about.gitlab.com
Maturity
1–10 of 127 posts
Re: Maturity
#2Somewhat unrelated, but I’d like to give a shout out to whoever designed Gitlab’s cookie consent interface. Rather than the usual “accept or gtfo” modal they allow you to choose which categories to select, and even list every individual cookie that will be issued, along with the origin, purpose, and expiry. My only criticism would be classifying a few cookies from Slideshare and/or LinkedIn as necessary because they share a name with Gitlab’s own Cloudflare cookies.
At some point tomorrow once I’m on an actual computer I’m going to have a dig and verify that they also don’t cookie you until you’ve consented - if that the case then I’m deeply impressed.
Re: Maturity
#3Somewhat unrelated, but I’d like to give a shout out to whoever designed Gitlab’s cookie consent interface. Rather than the usual “accept or gtfo” modal they allow you to choose which categories to select, and even list every individual cookie that will be issued, along with the origin, purpose, and expiry. My only criticism would be classifying a few cookies from Slideshare and/or LinkedIn as necessary because they…
They use Cookiebot: https://www.cookiebot.com/fr/
Re: Maturity
#4This is great, addressing a common and real criticism of gitlab that it seems has been in recent history much more focused on adding features than maintaining quality. The maturity schedule as I see it seems quite slow though, it shouldn't take years for a new feature to have high quality.
Re: Maturity
#5This is beautiful.
Made me think of https://www.reddit.com/r/dataisbeautiful, so I submitted it there https://www.reddit.com/r/dataisbeautiful/comments/d1xqfz/git....
Re: Maturity
#6> Lovable: Provides an elevated user experience that customers love as measured by NPS.
NPS = Net Promoter Score
Re: Maturity
#7This is great, addressing a common and real criticism of gitlab that it seems has been in recent history much more focused on adding features than maintaining quality. The maturity schedule as I see it seems quite slow though, it shouldn't take years for a new feature to have high quality.
The GitLab team will readily admit that they have a breadth first policy. This gives transparency for that policy, and does not change it.
Re: Maturity
#8I was sucked in by Gitlab's feature list and marketing. But holy shit so many things are half assed and so many features are buggy and broken. Like their wikis would sometimes just straight up delete text and their webhooks would break images. I started a bunch of issues but they really have no chance of getting fixed anytime soon. Just shows how different your impression of something is after actually using it.
Re: Maturity
#9I love using Gitlab SCM, but I'm surprised that Gitlab CI is described as "Lovable" while major bug fixes are gated for months on an uncertain future feature release:
"Job marked as success when job terminate midway in Kubernetes" https://gitlab.com/gitlab-org/gitlab-runner/issues/4119
IMO a production CI bug that falsely reports success merits a high priority patch release but Gitlab doesn't seem to see it that way.
Re: Maturity
#10> Lovable: Provides an elevated user experience that customers love as measured by NPS. NPS = Net Promoter Score https://en.wikipedia.org/wiki/Net_Promoter
Not sure why NPS is being used everywhere these days. Basically it makes all levels of "bad" just as bad as each other. What's so hard about using distributions?