1
0
Fork
You've already forked fep
0
forked from fediverse/fep
Fediverse Enhancement Proposals
  • Markdown 100%
2022年11月27日 23:08:09 +00:00
feps Merge pull request 'FEP-c390: Add missing contexts' ( #35 ) from silverpill/fep:identity-proofs-update-1 into main 2022年11月27日 23:08:09 +00:00
ISSUE_TEMPLATE ISSUE_TEMPLATE/tracking_issue.md: Add template for tracking issue 2021年01月04日 09:04:49 +01:00
EDITORS.md EDITORS: add Arnold Schrijver 2021年09月16日 14:24:47 +02:00
fep-0000-template.md FEP-a4ed: Draft updates 2020年11月25日 18:02:50 +01:00
LICENSE init 2020年10月06日 17:57:15 +02:00
README.md Add FEP-c390 to the Overview table 2022年11月23日 19:47:06 +00:00
SUBMISSION.md SUBMISSION: Move to codeberg.org. 2021年10月25日 09:42:53 +02:00

Fediverse Enhancement Proposals

This is the Git repository containing Fediverse Enhancment Proposals (FEPs).

A Fediverse Enhancement Proposal (FEP) is a document that provides information to the Fediverse community. The goal of a FEP is to improve interoperability and well-being of diverse services, applications and communities that form the Fediverse.

FEPs

Title Status Tracking issue dateReceived dateFinalized (or dateWithdrawn)
FEP-a4ed: The Fediverse Enhancement Proposal Process FINAL #10 2020年10月16日 2020年01月18日
FEP-8fcf: Followers collection synchronization across servers FINAL #6 #11 2020年10月24日 2022年02月07日
FEP-f1d5: NodeInfo in Fediverse Software DRAFT #12 2020年12月13日 -
FEP-400e: Publicly-appendable ActivityPub collections FINAL #5 2021年02月16日 2020年02月04日
FEP-8c3f: Web Monetization DRAFT #3 2022年01月18日 -
FEP-e232: Object Links DRAFT #14 2022年08月01日 -
FEP-5624: Per-object reply control policies DRAFT #18 2022年08月23日 -
FEP-1b12: Group federation DRAFT #22 2022年11月12日 -
FEP-8b32: Object Integrity Proofs DRAFT #29 2022年11月12日 -
FEP-c390: Identity Proofs DRAFT #34 2022年11月23日 -

Submitting a FEP

Do you have an idea, opinion or information that you want to share with the wider Fediverse community? You may do so with a Fediverse Enhancement Proposal (FEP).

To create and submit a FEP:

  1. Think of a title for the FEP you want to submit.
  2. Compute the identifier of the FEP by computing the hash of the title. This can be done with following Unix command:
$ echo -n "The title of my proposal" | sha256sum | cut -c-4
b3f0
  1. Clone this repository.
  2. Copy the FEP template (fep-0000-template.md) to the feps/ folder and change the filename to fep-abcd.md where abcd is the identifier computed in step 2.
  3. Write down your idea in the newly created file.
  4. Submit a Pull Request to this repository containing your proposal (other submission methods may be listed in SUBMISSION.md).
  5. Within 7 days you will receive feedback from the editors who may request changes or clarifications. If your proposal is accepted it will be added to the repository with the status DRAFT. The editors will also create a tracking issue for your proposal.
  6. You (as author) are now responsible for initiating community discussion and collecting feedback (post links to the discussions to the tracking issue). While the proposal is in status DRAFT you may submit changes to the proposal via Pull Requests (reference the tracking issue from the Pull Request).
  7. After at least 60 days of being added to the repository with status DRAFT you may request the proposal to be finalized. You must now request final comments from the community. If there are no significant community objections your proposal will reach status FINAL after 14 days. Once the proposal has reached status FINAL it may no longer be updated.

For more information see FEP-a4ed: The Fediverse Enhancement Proposal Process.

Editors

Editors are listed in the EDITORS.md file.

Copyright

CC0 1.0 Universal (CC0 1.0) Public Domain Dedication

To the extent possible under law, the authors of this document have waived all copyright and related or neighboring rights to this work.