1
0
mirror of https://codeberg.org/fediverse/fep.git synced 2026-08-05 11:46:04 +00:00

Provide example of using email address in "authors" field

This commit is contained in:
silverpill
2023-09-09 11:40:51 +00:00
parent 4f579275ae
commit 1536e995e7
2 changed files with 3 additions and 3 deletions
+2 -2
View File
@@ -1,6 +1,6 @@
---
slug: "xxxx"
authors: Alyssa P. Hacker <@alyssa.p.hacker@social.example>, Chatty Ben <@ben@chatty.example>
authors: Alyssa P. Hacker <alyssa.p.hacker@email.example>, Chatty Ben <@ben@fediverse.example>
status: DRAFT
dateReceived: 1970-01-01
---
@@ -15,7 +15,7 @@ dateReceived: 1970-01-01
## References
- [ActivityPub] Christine Lemmer Webber, Jessica Tallon, [ActivityPub](https://www.w3.org/TR/activitypub/), 2018
- [ABC] Alyssa P. Hacker, [An example proposal](http://example.org/abc.html), 2020
- [ABC] Alyssa P. Hacker, [An example proposal](http://abc.example/abc.html), 2020
## Copyright
+1 -1
View File
@@ -56,7 +56,7 @@ Proposal metadata is placed at the top of the document as key-value pairs betwee
Following metadata key-value pairs may be placed at the top of a proposal:
- `authors`: A comma separated list of authors of the proposal. Each item of the list should contain an author's name followed by a contact address in angle brackets (e.g. `Name <@alyssa.p.hacker@social.example>`).
- `authors`: A comma separated list of authors of the proposal. Each item of the list should contain an author's name followed by a contact address in angle brackets (e.g. `Alyssa P. Hacker <alyssa.p.hacker@email.example>`, `Alyssa P. Hacker <@alyssa.p.hacker@fediverse.example>`).
- `status`: Indicates the proposal status. Can be either `DRAFT`, `WITHDRAWN` or `FINAL`.
- `dateReceived`: Date of when the proposal was added to the repository (when status is set to `DRAFT`).
- `dateWithdrawn`: Date of when the proposal status was set to `WITHDRAWN` (only for proposals with status `WITHDRAWN`).