Requests for Comment

RfC creation instructions
Following are some of the instruction to open a request for comment. Before following these steps you are strongly recommended to create a draft proposal and invite users for feedback.
 * 1) To create a new RfC type the name of the RfC in the below box and click "New Proposal". Describe the RfC in detail.
 * 2) After your have finished writing the RfC, add it in the open requests section of this page.
 * 3) Update RecentChanges/Community with the link to newly created RfC.

Open requests

 * Requests for Comment/Replace reCAPTCHA with another CAPTCHA 2

Draft requests

 * Requests for Comment/Request for Oversight Authority

2021

 * Local (Meta) Local IP Block Exemption
 * Creating a blocking policy for all wikis
 * Changes to the Dormancy Policy (2)
 * Central notice changes
 * Changing the Powered by Miraheze footer button
 * Improvements for notification of global discussions
 * Landing page redesign
 * Community Directors (Amendments)
 * Dormancy policy exception for larger wikis
 * Restore old CAPTCHA
 * Window between wiki requests
 * Community Disputed Wiki Closures
 * Global ban for Blubabluba9990
 * Adding Reception Wikis as a separate wiki category
 * IRC/Replacement of default chat platform in WebChat extension (IRC participants only)
 * Abolishing the Dormancy Policy
 * Local (Meta) Icons and wordmarks
 * The future of Miraheze-run IRC channels (IRC participants only)
 * Allow global sysops to globally rename users
 * Abolish the Code of Conduct Commission
 * Discord RfC 2

2020

 * Ban Foe Requests
 * Topic ban Reception wikis
 * Local (Meta) Autopatroller group split
 * Global Rollback group
 * Require that RfCs undergo a public comment period‎‎
 * Code of Conduct Commission reform
 * Local (Meta) Use of the interface administrator group on Meta
 * Prohibit hate-based wikis
 * Local (Login Wiki) Opt in Miraheze Login to Global Sysop administration
 * CVT reform
 * Examknow appeal
 * NordVPN
 * Harassment Guidelines
 * Community Ban for PlavorSeol
 * Local (Meta) User close policy

2019

 * The Definition of Harassment and Related Terms
 * Community Directors
 * Followup to the Examknow RfC
 * Changes in some restricted settings
 * Examknow
 * A request to add more admins and stewards
 * Amendment of Stewards policy and Proposing yearly steward elections
 * Changes to the Dormancy Policy
 * Eligibility criteria to apply for CVT and Steward
 * Local (Meta) Meta administrator and bureaucrat policies
 * Interwiki-admin changes
 * Changes to the Content Policy
 * Local (Meta) Blocking policy
 * CVT policy
 * Username policy (2)
 * RfC/U process
 * No open proxies policy
 * Discord RfC 1

2018

 * Amanda ban appeal
 * Interwiki links editing
 * Globally mutual interwiki links among all Miraheze wikis‎‎
 * Miraheze Commons - a common image repository for Miraheze
 * A request to enable Semantic MediaWiki on Miraheze
 * Future of Wikicreators

2017

 * A request to establish the communities view on stewards and how they should be managed.
 * Create policies to manage unlicensed files that come from the community.
 * Achieve consensus regarding potential local use of OS and CU tools.
 * The effect of Steward and Sysadmin global rights on local communities.
 * Make a policy regarding local use of CU/OS tools
 * Community-imposed ban on a single user
 * Include a top-level category link in the sidebar
 * Global on-wiki chat software
 * Policy regarding open proxies and conditions on user accounts
 * Reverse community on User:Lawrence-Prairies
 * Change to Steward Policies
 * Policy to document ALL existing policies on Meta
 * Allow exception to LP ban
 * Code of Conduct
 * Changes to CVT group
 * Review exception to LP ban and reban them
 * Username policy
 * Amendment of Code of Conduct, September 2017
 * CVT changes