Feedback AFTER the FEP-a4ed became FINAL …
- This topic was moved from: FEP-a4ed: The Fediverse Enhancement Proposal Process
- To discuss document changes: #8 - Clarify how to correct, extend, supercede FEP with FINAL status - fep - Codeberg.org
A particular FEP has become FINAL
and the FEP process states …
A proposal with status
FINAL
can not be changed or updated.
Now suppose I would like to change it. What’s the procedure? Should one write another FEP that suppercedes the current one if it becomes FINAL. If so, how do we document that so it is clear to everyone? Or should FEP’s be Versioned instead?
The change I am thinking about is following:
- While in
DRAFT
mode there should not be a Timer that is ticking (the 60 day period). This is the stage where you prepare your proposal before it is ready for the world. - Add an additional workflow step
PROPOSED
where the 60-day review period starts.
The workflow then looks as follows:
+-------+
+-------> | FINAL |
| +-------+
+-------+ +----------+ |
-------->| DRAFT | -------->| PROPOSED |--------+
+-------+ +----------+ |
^ | +-----------+
| +-------> | WITHDRAWN |
| +-----------+
| |
+--------------------------------------------------+
Why extend?
- So all drafts being prepared are in one place.
- So you can work with others to hone it together before actually proposing.
For the case where a new FEP supercedes another this may be reflected in its state, plus a reference to the superceding FEP is added to the old one. Maybe a better state name is in order e.g. ARCHIVED
or even (maybe) DEPRECATED
in some cases…
+-------+ +------------+
+-------> | FINAL |--[other-FEP]-->| SUPERCEDED |
| +-------+ +------------+
+-------+ +----------+ |
-------->| DRAFT | -------->| PROPOSED |--------+
+-------+ +----------+ |
^ | +-----------+
| +-------> | WITHDRAWN |
| +-----------+
| |
+--------------------------------------------------+