7 ms·
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
by MattIPv4 3y ago
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."
- mmcwilliams 3y agoAlso got an email but interestingly the most populated group I'm a member of has 4 users in it including myself. It did mention that my "top-level" group has reached the 5-member limit but it references a numerical ID that doesn't match my user or any of the groups I'm member to. There may be a glitch with this rollout.
- mike-cardwell 3y agoYeah, I got the same email. I am in one group, and that group has one other person in it.
- xx_ns 3y agoI'm in exactly 0 groups, never been in one, and I got the same email.
- john_cogs 3y agoGitLab 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/ https://about.gitlab.com/blog/2022/03/24/efficient-free-tier...
- Nouser76 3y agoI don't know that it's a great plan to do a blogpost and in-app notification as the first round of reminders and email on the day of the change. Both the blogpost and in-app notification requires you to explicitly go on GitLab and see there's a problem. Maybe there's a reason to avoid it, but emailing from the get-go seems like it is the right move for transparency and not rug-pulling. EDIT: clarified antecedent
- LegitShady 3y agoWouldn’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.”
- Brian_K_White 3y agoLook 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.
- alex3305 3y ago> 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. I think there is a glitch in your mail or something else is going wrong. I'm currently not in any groups and still got an e-mail telling me that my top level group (starting with 5060) has reached the 5 members limit. Searching for the group also doesn't yield any results whatsoever.
- john_cogs 3y agoThanks, we are investigating this and the above reports about this behavior.
- crossroadsguy 3y agoI did receive an email too which just had a number mentioned that wasn’t even hyperlinked to anything. Turns out I am or was not part of any group ever.
- LaundroMat 3y agoMy email mentions two group id's. I had to look at each group's page to see its id (no other way of finding out what group we're talking about). I have _no_ groups with the id's mentioned in the email. Also, I'm a solo hobbyist dev, there are no groups with more than one user in it.