mirrors/fep
1
0
Fork 0
mirror of https://codeberg.org/fediverse/fep.git synced 2026-08-05 19:55:46 +00:00
Code Packages Wiki Activity

How to update FEP-a4ed (#180)

Browse Source 
#134

Reviewed-on: https://codeberg.org/fediverse/fep/pulls/180
Co-authored-by: silverpill <silverpill@firemail.cc>
Co-committed-by: silverpill <silverpill@firemail.cc>
This commit is contained in:
silverpill
2023-10-28 14:48:14 +00:00
committed by David Sterry
parent 0c1ea095f9
commit 5ad552e55f
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
fep/a4ed/fep-a4ed.md
+5 -1
View File
@@ -125,10 +125,14 @@ A list of editors is maintained in the `EDITORS.md` file at the root of the FEP
A list of methods in which a proposal may be submitted is maintained in the `SUBMISSION.md` file at the root of the FEP repository.
### FEP-a4ed
### FEP Process Governance
FEP-a4ed (The Fediverse Enhancement Proposal Process) is a living document and can be updated despite having the `FINAL` status.
Anyone can propose a change to FEP-a4ed (or other documents related to the FEP process) using any method listed in `SUBMISSION.md` file. The change must be approved by at least two editors (one of them could be the submitter). For any part of the FEP process, there must be a sufficient number of editors who agreed to do the maintenance work. Changes should not be accepted before at least 1 month passes after the last update, to give editors and the community time to review them and provide feedback.
Minor changes (i.e. a correction of a typo or of a broken link) can be accepted immediately after getting two approvals from editors.
## History
The process and format described in this proposal is influenced by other community driven documentation efforts such as the BitTorrent Enhancement Proposal Process [BEP-1], Scheme Request for Implementation [SRFI] and the IETF RFC Series [RFC-8729].