FEP-a4ed: The Fediverse Enhancement Proposal Process

[trwnh]

@trwnh

i think it is a good idea to practice “asset colocation” and keep FEP-specific files stored within the FEP-specific directory. what’s “confusing” is that we have essentially three current paths that FEP submitters have to be aware of:

• feps/fep-xxxx.md
• feps/assets/fep-xxxx/filename.ext
• contexts/fep-xxxx/context.jsonld (pending 2e40 or 9606)

there is additionally an issue of unclear editing authority. better to avoid write conflicts and just give each FEP editor an FEP-specific directory.

are there any objections to this? i think i’m just going to do it as a PR

to clarify, this is the current plan:

migrate feps/ to fep/xxxx

• /fep/xxxx/index.md or readme.md or fep-xxxx.md (not sure what to specify exactly; weak preference for index.md, because this will make static site generation easy; secondary preference for fep-xxxx.md because this retains the filename; weakest preference for readme.md because this will show up in codeberg markdown preview for the /fep/xxxx folder)
• /fep/xxxx/assets/whatever.png
• /fep/xxxx/context.jsonld (usage specified in 9606)

/feps/fep-xxxx.md remains as legacy; it is expected to migrate away from using this, perhaps by editing existing files to point to the new location? something like /feps/fep-xxxx.md can be edited to contain something like this:

[moved to /fep/xxxx](https://codeberg.org/fediverse/fep/src/branch/main/fep/xxxx/)

or otherwise a symlink, which doesn’t work in codeberg’s markdown preview (see [Better symlink support] Follow relative symbolic links in GUI if they are available · Issue #12219 · go-gitea/gitea · GitHub for that issue i guess) but works on pretty much anything else that interfaces with a filesystem:

../fep/xxxx/

of the two, i have a slight preference for the markdown link because i expect the majority of people looking at the old file path to be doing so on codeberg, not in a locally cloned copy of the repo (where the structure should be clear, because they have the whole repo already)