zlacker

>>MattIP+(OP)
Just got an email from GitLab about a group I'm part of that has more than five users. The docs linked says "For existing namespaces, this limit is being rolled out gradually. Impacted users are notified in GitLab.com at least 60 days before the limit is applied.", however upon checking the group in GitLab, we are greeted by a big red box stating "Your top-level group [group] is over the 5 user limit and has been placed in a read-only state."

>>MattIP+d
GitLab team member here.

The gradual roll out of this change started with a blog post[0] and included in-app notifications for the owners of impacted groups on GitLab.com.

If the group owner did not log in during the in-app notification period, they were then emailed (the email you received today) notifying that the group was impacted.

[0] - https://about.gitlab.com/blog/2022/03/24/efficient-free-tier...

>>john_c+xb
Wouldn’t it make more sense to email them before they were impacted instead of when they were impacted? What’s the point of gradual roll out that requires I read your blog etc. An email that says “You have 60 days to X” is a lot more effective than one that says “60 days ago we made a blog post letting you know, and now you’re f’d.”

>>LegitS+Yn
Look they announced it publicly posted right in the back of the file cabinet in the basement behind the warning rabid tigers sign.

Here's a question for Gitlab: "Why did you require me to give you an email address to sign up?"

The answer to that question means there is no explaining why they didn't use it first, and followed up with at least a couple updates along the way. This is exactly what the address exists on thier db for.