FEP-a4ed: The Fediverse Enhancement Proposal Process

Since no objections have been made, I think it’s time to move forward.

New directory layout

I don’t disagree with the proposed layout. The only thing that appears to be broken is redirections, and I’m going to fix them at least for my own proposals. Another, relatively minor issue, is the new slug metadata field, which is not documented in FEP-a4ed. Is it really needed? There should be a way to make static site generator generate nice URLs without adding clutter to FEP documents. @trwnh

New FEPs

Four new FEPs are awaiting editors’ approval. Is there anything that prevents them from being accepted into the FEP repo?

New editors

@helge, is it true that you’re now a FEP editor? I fully support this move. Shouldn’t EDITORS.md file reflect this change?

FEP governance

I don’t think this is a good practice. FEP process is very important part of the Fediverse, and it should be predictable. Here’s what I propose:

  1. Significant changes to FEP process should be reviewed by the majority of editors. The length of the review period should be specified in FEP-a4ed (e.g. one week since last commit).
  2. Proposals should not be changed or moved without author’s consent.