AVID:Requests for Comment/Screen ALL future RfCs

Screen ALL future RfCs
Lately, I've noticed an influx of under-thought, half-baked Requests for Comment, to the point of the RfC landing page being clogged with heavily opposed RfCs. I'm proposing that a system to screen RfCs be implemented in order to keep proposals to a certain standard of quality. I have two possible options in mind, which will be outlined below. (Lets chat!) 04:30, 21 May 2023 (UTC)

Send all RfCs to a staff screening queue
This proposal would be similar to the Moderator extension, where any RfCs are sent to a queue where AVID staff will discuss the pros and cons of such a proposal, and whether there has been enough thought put into it.

Oppose

 * 1) Absolutely not. There could be censorship behind this process, which given that there is no publicly available general criterion that users can reference if they believe that rejection has been made in bad-faith. -- Cheers, Bukkit (talk • contribs • global • rights) 04:53, 21 May 2023 (UTC)
 * 2) As Bukkit pointed out, censorship could be behind this process. That's not good for me (or the site), so for that reason, I'm out. (I have no idea on the third proposal, and I think the second proposal is the best out of the three.) User:AUnnamedDragon 9:50 AM, May 21, 2023 (CET)


 * An understandable concern. I can assure you, having worked with AVID staff for a while, that we would not work to censor our users. Given your position on the matter, I encourage you to consider the second proposal provided here. Eternity Media Group Wordmark.png (Lets chat!) 07:14, 21 May 2023 (UTC)
 * I'm not concerned with the current staff roster, I'm more concerned about the future generations. This just seems to be a hotfix that is gonna shoot everyone in the foot at some point. -- Cheers, Bukkit (talk • contribs • global • rights) 19:05, 21 May 2023 (UTC)
 * Yeah fair enough. Again, I encourage you to consider the other proposals provided here. Eternity Media Group Wordmark.png (Lets chat!) 10:56, 22 May 2023 (UTC)

Implement an RfC draft system
This would be similar to the RfC draft system at meta.miraheze.org.

Support

 * 1) for either, but this one is the best. Drafting would help people like me fix the RfCs we make. I might word something wrong, break grammar, or forget it is already implemented. JrStudios Logo .png(What you gonna do when clip-ons come for you!?) 11:49, 22 May 2023 (UTC)
 * 2) I'm vouching for this one. I think this would ensure the right RFCs that will get approved   Logohub   (talk) 07:20, 21 May 2023 (UTC)
 * 3) as proposer for this option. Eternity Media Group Wordmark.png (Lets chat!) 07:40, 21 May 2023 (UTC)
 * , we seriously NEEDED this for a long time. It took several months from when this first got proposed on Discord to when it finally showed up on an RfC. I bet this feature is going to be a lifesaver for many people on the Staff to screen those half-baked RfCs some have been putting out ever since its introduction. Why haven't we got started on this sooner? Compooper (talk) 11:01, 21 May 2023 (UTC)
 * 1) per others. T807sig.png · Talk · Edits 12:47, 21 May 2023 (UTC)
 * 2) Great for rush hour! Ashley Taylor ft. Cure Finale (soulbond) and Raboot (pet) (talk) 13:46, 21 May 2023 (UTC)

A Hybrid System
As proposed by Raidarr on the Discord server, this idea would see what is primarily a draft system, with a to be determined amount of time in draftspace, alongside the requirement of 2 members of site staff signing off on the proposal before it appears on the RfC landing page. (Lets chat!) 12:12, 21 May 2023 (UTC)

Support
A good option. Anything to filter useless RFCs like "Ban [Important feature], or "Return scare factor!1!1" (What you gonna do when clip-ons come for you!?) 11:51, 22 May 2023 (UTC)

Oppose

 * 1) Same reason for opposition as proposal 1. -- Cheers, Bukkit (talk • contribs • global • rights) 12:05, 22 May 2023 (UTC)