# FEP-a4ed: The Fediverse Enhancement Proposal Process

**URL:** <https://socialhub.activitypub.rocks/t/fep-a4ed-the-fediverse-enhancement-proposal-process/1171>\
**Category:** Fediverse Enhancement Proposals\
**Tags:** fep-a4ed, fep, final\
**Created:** [December 1, 2020, 5:19pm UTC](https://socialhub.activitypub.rocks/t/fep-a4ed-the-fediverse-enhancement-proposal-process/1171 "2020-12-01T17:19:20Z")\
**Posts on this page:** 1\
**Showing post:** 112

<div class="post-metadata">

**Author:** ![stevebate](https://socialhub.activitypub.rocks/user_avatar/socialhub.activitypub.rocks/stevebate/32/2763_2.png) [@stevebate](https://socialhub.activitypub.rocks/u/stevebate)\
**Post date:** [September 24, 2023, 8:13am UTC](https://socialhub.activitypub.rocks/t/fep-a4ed-the-fediverse-enhancement-proposal-process/1171/112 "2023-09-24T08:13:41Z")

</div>

Many MarkDown applications use YAML for frontmatter. The current FEP frontmatter is technically YAML-compatible, but if some fields like `authors` were YAML lists (of name/value objects?), it would be easier to process the metadata. Currently, one needs to parse the comma-separated string into a list of name/email pairs.

---

_[View the full topic](https://socialhub.activitypub.rocks/t/fep-a4ed-the-fediverse-enhancement-proposal-process/1171)._
