|pukkamustard 863657c192||pirms 1 gada|
|ISSUE_TEMPLATE||pirms 2 gadiem|
|feps||pirms 1 gada|
|EDITORS.md||pirms 1 gada|
|LICENSE||pirms 2 gadiem|
|README.md||pirms 1 gada|
|SUBMISSION.md||pirms 2 gadiem|
|fep-0000-template.md||pirms 2 gadiem|
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.
|FEP-a4ed: The Fediverse Enhancement Proposal Process||
|FEP-8fcf: Followers collection syncrhonization across servers||
|FEP-f1d5: NodeInfo in Fediverse Software||
|FEP-400e: Publicly-appendable ActivityPub collections||
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:
$ echo -n "The title of my proposal" | sha256sum | cut -c-4 b3f0
abcdis the identifier computed in step 2.
DRAFT. The editors will also create a tracking issue for your proposal.
DRAFTyou may submit changes to the proposal via Pull Requests (reference the tracking issue from the Pull Request).
DRAFTyou 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
FINALafter 14 days. Once the proposal has reached status
FINALit may no longer be updated.
For more information see FEP-a4ed: The Fediverse Enhancement Proposal Process.
Editors are listed in the EDITORS.md file.
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.