To each FEP there, a local topic here is tracked below, under the fep tag and another tag named after the FEP code, e.g., fep-a4ed. Everyone can discuss FEPs here and propose changes in the repository.
Making a New Proposal
A FEP usually follows from a conversation. Once the conversation starts shaping up, it’s time to make a formal submission. Once the newly created FEP is available from the repository, a new topic is created in the #activitypub:fep category by @activitypub.hosts.
Once a FEP is FINAL, the draft tag is replaced by a final tag, and the FEP content can be pasted to the first post (retaining the original link to the repository) to be published. The published page will be available at, e.g., /pub/fep-a4edc7b-the-fediverse-enhancement-proposal-process, and can be referenced in documentation.
FEP Tracker
The FEP trackers watches the FEP repositories to create an up-to-date index.
Ah no, not that I know of. I didn’t even think of checking here. On all the other forums I’m at the About [Category] pages mostly serve to give a short description in the Category UI. Manual cross-ref of individual FEP’s is done and the topic link pasted into the TRACKING issues on Codeberg.
Can’t create new topics here so asking in this one.
Suppose I need to update something in a FEP that is already final. For example, to add new features to that particular AP extension, or to clarify the intended behavior, or provide more examples. What would be the process for that? IETF RFCs, for example, work such that the updated version is published as a new RFC with a new number, but it gets a special tag that it updates a previous RFC, which itself gets a tag that an updated version is available.
Although recent and upcoming changes in Discourse may be useful to automate the index, I guess using the FEP Tracker Tool might be a better short term solution (as to externalize the tracker and keep it up-to-date for visitors.)