Permit users to block other users [from interacting with their namespace].
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
When a user is disruptive to another, disallowing them from interacting the user's entire namespace may be preferable to merely disallowing them interacting with specific repositories.
Intended users
Individual users, that have created content under their namespace.
Proposal
Permit users to block other users from interacting with at least their repositories and snippets.
Permissions and Security
A user should solely be able to block another from that which they own and created. All else is tracked by gitlab-org/gitlab/-/issues/351343.
Documentation
This should be documented, as it is at GitHub.
Availability & Testing
Because this disallows interaction, any implementation should be stringently evaluated.
Available Tier
Free
Feature Usage Metrics
It should be tracked, but I don't know how.
What does success look like, and how can we measure that?
When a user is able to add another to their block list, and doing so prevents that user interacting with their repositories and snippets.
What is the type of buyer?
Existing users experiencing spam and/or harassment.
What is the competitive advantage or differentiation for this feature?
It provides feature parity with GitHub.
Links / references
-
Originally discussed at
issues/351343#note_1717293302. -
For examples, see: