AVID:Requests for Comment/Clarify Who can close a proposal: Difference between revisions
| Line 38: | Line 38: | ||
===Comments=== |
===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). --[[User:Raidarr|Raidarr]] ([[User talk:Raidarr|talk]]) 13:56, 3 March 2023 (UTC) |
|||
[[Category:Requests for Comment]] |
[[Category:Requests for Comment]] |
||
__NOTOC__ |
__NOTOC__ |
||
Revision as of 13:56, 3 March 2023
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
Abstain
Oppose
Comments
2. Bureaucrats and Admins
A bureaucrat or an admin is capable of closing (admins only in the case of SNOW closure or author retraction)
Support
Abstain
Oppose
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
Support, because it really makes sense to allow all staff to do it. 
13:08, 3 March 2023 (UTC)
Abstain
Oppose
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)
