Technical Implementation of CoC Mailing-list stuff
--------------------------------------------------
Key:
POST = effectable after a flame is public
PRE = effectable before a flame is public
Requirements:
1. Ability to lock threads. (POST)
2. Ability to temporarily block posts from a given user. (POST)
3. Remove users from the ML entirely. (POST)
4. Block a specific post if N reviewers agree. (PRE)
5. Issue reject messages for 1-4.
6. The above should not always need infra to perform them -
   otherwise they cannot be performed in a timely manner.

Infra already have the ability to do #2 and #3, but exercise
it with great caution - #3 is only used when developers
retire thus far, while #2 has never been used.

#3 does need to be generally available if #2 is available to
reviewers first, and can remain a devrel/infra ability to
avoid abuse.

For implementation process, we are going to prioritize some
of the requirements, so that we can deliver some of the
requirements as soon as possible.

Stage -1
========
This is the present state of affairs. Proctors need to ask infra to do
everything, and only #2 and #3 are usable.

Stage 0
=======
Develop framework/modifications to mlmmj to enable proper
use of requirements.
Status: Already in progress

Stage 1
=======
Implement #2 by using access-list writing temporarily.
Status: Already in progress.

Stage 2
=======
Implement #2 and #5 using framework.
Status: Not yet started.

Stage 3
=======
Implement #1 using framework, requires keeping state.
Status: Not yet started

Stage 4
=======
Implement #4 using framework, requires a full interface.
Status: not yet started