Allow per-project/group/user muting for User Self-Moderation
Problem to solve
Allowing Users to self-moderate what they see and who they interact with. This capability will allow our Users to decide what they want to see, what they want to work on, who they want to interact with and better aligns us with industry standards.
Intended users
All Gitlab Users
Further details
Benefits:
- Improved User Experience by allowing Users to Self-Moderate.
- Reduced operational load related to Abuse reports.
- Provides the ability to better prioritise reports of abusive behaviour based on the amount of User blocks applied to a specific user.
Proposal
Provide Users the ability to "Soft Block" other Users which would:
- Hide the Blocked Users Comments/Issues/MR's/Snippets/Reaction's from Blocking Users view.
- Does not notify the Blocking User if they were tagged/CC's by the Blocked User.
- Does not allow the Blocked User to add Blocking User to any projects
- Allow users to define who could tag them in Comments/Issues/MR's/Snippets (example: only people with a
@abc.com
email address)
Secondary:
- Does not automatically add Users to projects without their consent.
Documentation
Possibly: https://docs.gitlab.com/ee/user/permissions.html and https://docs.gitlab.com/ee/user/project/members/
What does success look like, and how can we measure that?
- Improved User experience (unable to determine how to measure it at this stage)
- Reduction in false positive Abuse reports related to Code of Conduct Violations
Links / references
Edited by Charl de Wit