rfcs/0000-using-rfcs.rst:
Add a first, fairly simple (most of the relevant **Specification**
information is found in the README of the repository) RFC about using
the RFC system to steer Arch Linux.
Add a section about existing (fairly recent) documentation in the wiki.
Add a few sentences to outline the different entities Arch Linux
consists of and what the RFC process is improving upon.
Clarify the setup of the final comment period, after which the RFC is
either accepted or rejected.
Expand upon how and why the specialized communication channels are
insufficient for solving overarching topics.
Specify that the discussion takes place in the merge request itself.
Add information on how RFC ideas may be proposed and existing ones
browsed.
Expand specification section by a paragraph on who is allowed to create
an RFC (anyone) and explain what are the limitations for outside
contributors (they can only create an RFC if at least one Developer or
Trusted User supports the topic and helps to develop it).
Elaborate on how in the current situation the decision making process or
found consensus may be oblique to newcomers (or even long term staff)
and that RFCs serve as an ongoing standardized archive of discussions
and found consensus.
Mention GitLab's approval feature as a means to approve of an RFC
alongside the possibility to leave a comment for a more nuanced motion.