Requests for comment/Archive 3

MediaWiki developers and users draft ideas for the future of MediaWiki in Requests for comment. They are part of a review process to achieve consensus, guided by the Architecture committee.

RFCs are usually only for proposing major changes to MediaWiki core, or to extensions that are already widely used, that may represent a new precedent not covered by our architecture guidelines. If you wish to create a new, or to make a minor core change, or one that will be likely to uncontroversial, there is no need to draft an RFC for it; go ahead and file a bug report, implement your change, and submit it in Gerrit for review. If you need advice on design decisions pertaining to such ideas, there are several other communication venues for making people aware of your proposal. See also planning a new extension.

If you want to propose an architectural or large change, consult the Request for comment process, then [ Create a new RFC on Phabricator]. As of 2016, the Architecture committee has started to assign RFCs to shepherds (see T125865).

Some RFCs on wiki
Below is a list of RFCs that have associated documents on this wiki. Wikis are a good platform for collaboration and for writing technical documentation (a spec). The lists below are out of date; refer to the ArchCom-RFC workboard in Phabricator for any RFC's current status.

In draft
  category = Draft requests for comment order = ascending ordermethod = sortkey 

Ready for discussion
  category = Proposed requests for comment order = ascending ordermethod = sortkey 

Stalled
  category = Stalled requests for comment order = ascending ordermethod = sortkey 

Accepted
  category = Accepted requests for comment order = ascending ordermethod = sortkey 

RFCs with bad status

 * Shouldn't happen – use a preset status  and optional   in RFC.

  category = RFCs with bad status order = ascending ordermethod = sortkey 

Archive
Archive of closed RFCs (either implemented or declined)