AVID:Requests for Comment/Clarify Who can close a proposal

Clarify who can close a proposal

I've noticed that there is not much clarity as to who can close an RFC among staff. AVID:Site Staff currently states that only a bureaucrat is capable of doing so. However I've seen on occasion some administrators have closed them. Hence, I am making the following three proposals to clarify who can close them. (Lets chat!) 07:24, 3 March 2023 (UTC)

1. Bureaucrats Only

Make it so officially only Bureaucrats can close RFCs.

Support

1. Support I elaborate in the last comment section. Basically, this process can have serious consequences. Letting any staff including developing ones such as moderator make judgement calls here invites problems. Even admins are not always qualified to judge edge cases, for example 'less important' rfcs that have 'less votes'. If they want to try they should do it in contact with a bureaucrat. If they're good at it then maybe they should just be bureaucrats. I need to see a stronger process to deal with edge cases and SNOW closures to vote for anything else. --Raidarr (talk) 13:59, 3 March 2023 (UTC)

2. Bureaucrats and Admins

A bureaucrat or an admin is capable of closing (admins only in the case of SNOW closure or author retraction)

Comments

 Comment: gonna be real, this is the proposal I'd be most likely to vote for had I not created the proposal. (Lets chat!) 13:34, 3 March 2023 (UTC)

You have every liberty to vote on a proposal you created, the only part that is discouraged is the closing bureaucrat voting on the proposal. --Raidarr (talk) 13:49, 3 March 2023 (UTC)

3. Any Member of Staff

Anyone with a staff role can close (Admins and below only in the case of SNOW closure or author retraction).

Support

1. Support, because it really makes sense to allow all staff to do it. 13:08, 3 March 2023 (UTC)

Comments

 Comment: There needs to be definition on 'how SNOW is SNOW'. I wouldn't be comfortable with just any moderator making this call as this proposal entails. Best practice would be only admins should make this call when it is very strictly clear to make, not just because they feel 'well it's going well/poorly so I'll close it now'. This invites confusion and possible chaos in a process that can have extreme consequences on a wiki. That is why for Miraheze in general, it is preferred these closures are only performed by bureaucrats in the first place. Unless we can get that fixed I'd rather this be decided at the bureaucrat level and if bureaucrats aren't catching up, see if someone qualified is willing to step up so their ranks are healthy. I'd be fine seeing admins perform some closures if, again, SNOW is better defined. If it is, this could extend to RfPs as well (in the case of too many opposes and/or withdrawal). --Raidarr (talk) 13:56, 3 March 2023 (UTC)

If you check the RFC landing page, you will see we do indeed have enforced stipulations for SNOW closure (Lets chat!) 14:02, 3 March 2023 (UTC)