FEP-a4ed: The Fediverse Enhancement Proposal Process

would it maybe be a good idea to restructure the repo such that FEPs each get their own subdirectory rather than having them all top-level under feps/? there are already some FEPs that contain “assets”, and soon i imagine (after FEP 2e40 or 9606), there will be FEPs that contain context documents and term definitions. it’s confusing to have it in the current layout. i propose the following:

  • /feps/fep-2100 => /fep/2100/index.md
  • /feps/assets/fep-2100/linksCollection.png => /fep/2100/assets/linksCollection.png

this came up while i was writing 9606. my initial idea was to use /contexts but this did not seem like a good idea to create yet another split-directory. we can avoid having to keep track of changing files in 3 different folders if we just create a single folder for each FEP.

at that point, you’d have the following required files:

  • /fep/xxxx/index.md
  • /fep/xxxx/context.jsonld (if defining new terms)

with anything else being optional:

  • /fep/xxxx/image.jpg (can be in an assets subfolder if desired)
  • /fep/xxxx/exampleTerm (a text file defining some term, if wanting to give a dedicated page)
1 Like