User:Tznkai/desk/BLPconcern/Stub and protect BLPs

Proposal: Stub-protection for low activity BLPs

I assume that most of you will agree that we have some sort of responsibility to control bad BLPs. In view of that, I have a potentially controversial, but hopefully compelling proposal.

Upon encountering a BLP with low editor activity, (Typified by less than one non-automated edit per month and/or cleanup tags over six months old) and also containing a BLP violation, any administrator may immediately do all of the following:
 * Reduce the article to a bare bones stub.
 * Tag it with a special stub template which links to articlename/sandbox
 * Report it to the BLP noticeboard. (or a new noticeboard)
 * Full protect the article indefinitely.

In order for this protection to be lifted, an active editor must volunteer to watchlist it, and an acceptable version of the article written must be already in the sandbox, which would then be history merged into the main article.

This would be replaced with a similar flag revision procedure if the features is ever enabled, but is a stop gap solution in the meantime. I think this would be a big leap forward in addressing a particular problem.