User:Chmod/RFC system proposal

From pisswiki
Revision as of 03:11, 25 October 2021 by Chmod (talk | contribs) (Created page with "== NOTE: If you want to suggest an edit, please make the page "User:<YOURUSER>/RFC_system_proposal" with the source from this page, and add it to [https://wiki.letspiss.net/in...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

NOTE: If you want to suggest an edit, please make the page "User:<YOURUSER>/RFC_system_proposal" with the source from this page, and add it to my talk page.

The current proposal is as follows:

RFC statuses

  • Draft: The proposal is in draft form and may be edited. People may comment in the talk page.
  • Finalizing: In this state, the proposal is considered ready to be discussed. A 7 day period is given for final discussion.
  • Rejected: The result after the finalizing state shows disapproval and the proposal is rejected.
  • Active: The result after the finalizing state shows there is agreement. The RFC will now become active.
  • Superseded: The contents of the RFC have been superseded by another RFC. The RFC is now inactive.

Lifecycle

  • Initial => Draft: The RFC has been proposed.
  • Draft => Finalizing: The RFC has been given enough time to be ready for final discussion.
  • Finalizing => Rejected: The RFC had enough opposition.
  • Finalizing => Active: The RFC had enough approval.
  • Active => Superseded: An update is made.

Notes about number assignation

The RFC would be initially created in the User:<YOURNAME>/RFC/<name> or similar, and then moved/copied to the RFC:<number> namespace. The number should not be reused.

Managers?

Should we assign some people to manage the system, and replace them if they leave/AWOL?

Format

Todo, help would be appreciated