Requests for Comment/User close policy

This RfC proposes a policy to close certain premature requests for privileges before they waste people's time. The proposal would only affect Meta.

Several Meta requests pages (notably Requests for Stewardship and its archive) contain requests for additional authority from very new users. The users might not understand the implications or might be trolling. Currently, only a Steward can close requests; typically, they don't close them until after much debate and voting. This RfC proposes to let any  or   user close inappropriate requests, guided by common sense and subject to override and protection against abuse.

For an analog, see Wikipedia's Not now information page.


 * Proposer: DeeM28 (talk) 10:23, 23 December 2019 (UTC)
 * Edited by 19:58 24-Dec-2019

Proposal 1

 * Autoconfirmed and confirmed users are allowed to close any request for permissions as unsuccessful (global rights and local rights) if it is clear to them that the request is being made too early by a largely inexperienced user. In case of any doubt or an unclear case they should leave it up to a Steward.

Support

 * 1) proposer. --DeeM28 (talk) 10:23, 23 December 2019 (UTC)
 * 2) . I suppose that would be nice, because we should assume good faith of older users. WickyHoney (talk) 01:53, 17 January 2020 (UTC)

Neutral
.
 * 1) "It is clear to" me that Proposer shouldn't be allowed to edit! No, seriously, can we define "too early" and "largely inexperienced user"?  It's a good idea to resolve that users other than Stewards be able to close requests that aren't credible, but can we agree on language that gives them some guidance?  This would help make those closures mechanical and avoid drama.   18:06 23-Dec-2019
 * maybe base it on the current votes? Can’t think of a solid enough definition that isn’t too weak or too strict and not babying. ~ RhinosF1 - (chat)· acc· c -  18:12, 23 December 2019 (UTC)
 * Well, if it is so nuanced that we can't codify how a volunteer should do it, maybe he shouldn't.  18:16 23-Dec-2019
 * Personally, SNOW closes require an air of common sense rather than black and white rules. ~ RhinosF1 - (chat)· acc· c -  18:18, 23 December 2019 (UTC)
 * I agree with Rhino, since before users did not vote for the black and white rules for eligibility we should also keep this up to common sense, we don't need to always have precise rules for everything in my view and we need to let users use their common sense. --DeeM28 (talk) 09:16, 24 December 2019 (UTC)

Proposal 2

 * Stewards may overturn any user closes if they believe that they are made in error.

Support

 * 1) proposer. --DeeM28 (talk) 10:23, 23 December 2019 (UTC)
 * 2) . Goes without saying that Stewards can correct errors resulting from delegating their tasks.   18:08 23-Dec-2019
 * 3) . Sounds good. WickyHoney (talk) 01:53, 17 January 2020 (UTC)

Proposal 3

 * If a user closes too many requests in error, Stewards may choose to deny them the right to close requests in the future.

Support

 * 1) proposer. --DeeM28 (talk) 10:23, 23 December 2019 (UTC)
 * 2) . Stewards, having delegated the power to close requests, should have the right to un-delegate it from any individual on terms they see fit.   20:04 24-Dec-2019
 * 3) . Sounds good. WickyHoney (talk) 01:53, 17 January 2020 (UTC)

Neutral

 * 1) Again, terms need to be defined. As Proposal 1 would give the power to all confirmed and autoconfirmed, does this mean that the offender gets de-confirmed?  Or do Stewards keep a separate list of Confirmed but not Trusted?  Appeals?  Rehabilitation?  Etc.   18:13 23-Dec-2019
 * Sorry for the confusion. They would still be confirmed but they would have a sort of 'topic-ban' to close requests. The rest is at the discretion of Stewards. --DeeM28 (talk) 09:16, 24 December 2019 (UTC)
 * "Too many" still needs to be defined, but I'll support and leave definitions in the hands of Stewards.  I had been thinking of "offender" as the newbie making foolish requests and not the confirmed user closing them.   20:04 24-Dec-2019