Support temporary user bans

NEW
Unassigned

Status

developer.mozilla.org
User management
--
enhancement
4 years ago
3 years ago

People

(Reporter: Janet Swisher, Unassigned)

Tracking

Details

(Whiteboard: [specification][type:change])

(Reporter)

Description

4 years ago
What feature should be changed? Please provide the URL of the feature if possible.
==================================================================================
When MDN was in MindTouch, there was a capability to specify when a user ban would expire, allowing the user to access the site after the ban expired. This enabled admins to set temporary bans for "minor" offenses, such as page damage due to ignorance rather than malice, or edit wars. (https://intranet.mozilla.org/Engagement/Developer_Engagement/MDN_Administration_Guide#Banning_policy for those who have access)

What problems would this solve?
===============================
Bans are currently reversible, but this has to be done manually. Admins have no mechanism to remind them to reverse a ban, so bans are typically permanent.

Who would use this?
===================
Admins would use the feature. Contributors would benefit by being less likely to be banned permanently for minor transgressions.

What would users see?
=====================
TBD, since banning is enacted through the Django admin panel. It would be nice to have either a date field for the expiration date, or a drop-down for duration (1 day/1 week/2 weeks/etc.)

What would users do? What would happen as a result?
===================================================
Admins would have the option of setting an expiration when creating a user ban. The banned user would be allowed to access the site after the ban expired.

Is there anything else we should know?
======================================
FWIW, the vast majority of bans we created back in the MindTouch days were temporary bans, usually two weeks or less. Sometimes a month.
Severity: normal → enhancement
Component: General → User management
You need to log in before you can comment on or make changes to this bug.