Proposed in Community-Wishlist-Survey-2016. Received 28 support votes, and ranked #58 out of 265 proposals. View full proposal with discussion and votes here.
Problem
From time to time, editors are blocked, but subsequently it is decided that there is some sort of reason that the block should not be regarded as a "black mark" on that editor's contributions. Such editors often feel alienated by the experience, and this problem is harmful to editor morale and retention. Presently, unless the unblock entry states explicitly what the caveat associated with unblocking was, there is no good way to "correct" a block log subsequently. (Clearly, re-blocking briefly just to make a new block log entry is a bad solution.)
Who would benefit
In an immediate sense, this would benefit a subset of editors who have been blocked, but ultimately it will make work easier for administrators and assist in community processes (such as requests for additional permissions) by clarifying things that are otherwise unclear.
Proposed solution
Enable administrators to make comment-only entries in block logs, without blocking or unblocking.
More comments: Obviously, projects that elect to make use of this feature will also need to establish policies governing when an administrator may or may not modify an entry a decision made previously by another administrator.
Technical details
- Create a new special page, Special:AnnotateBlockLog (name up for discussion)
- Requires block rights to use
- Has a field for Username or IP address, identical in functionality to Special:Block
- Has a field for the comment
- Create a new log type, block/comment, for the annotations
- When saving a comment using the special page (or, eventually, the API) create a new ManualLogEntry with the comment