Fediverse Enhancement Proposals (FEP) A common place for people to create drafts and follow lightweight rules for documenting technical details for other developers. Also see: https://socialhub.activitypub.rocks
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

README.md 2.2 KiB

1 year ago
1 year ago
1 year ago
1 year ago
  1. # Fediverse Enhancement Proposals
  2. This is the Git repository containing Fediverse Enhancment Proposals (FEPs).
  3. 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.
  4. # Submitting a FEP
  5. 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).
  6. To create and submit a FEP:
  7. 1. Think of a title for the FEP you want to submit.
  8. 2. Compute the identifier of the FEP by computing the hash of the title. This can be done with following Unix command:
  9. ```
  10. $ echo -n "The title of my proposal" | sha256sum | cut -c-7
  11. b3f0afb
  12. ```
  13. 4. Clone this repository.
  14. 3. Copy the FEP template ([fep-0000000-template.md](./fep-0000000-template.md)) to the [feps/](feps/) folder and change the filename to `fep-abcdefg.md` where `abcdefg` is the identifier computed in step 2.
  15. 4. Write down your idea in the newly created file.
  16. 5. Submit a Pull Request to this repository containing your proposal.
  17. 6. 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`.
  18. 7. You are now required to initiate community discussion and collect feedback. While the proposal is in status `DRAFT` you may submit changes to the proposal via Pull Requests.
  19. 8. 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 now 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.
  20. For more information see [FEP-a4edc7b: The Fediverse Enhancement Proposal Process](./feps/fep-a4edc7b.md).
  21. # Editors
  22. Editors are listed in the [EDITORS](EDITORS) file.
  23. # Copyright
  24. CC0 1.0 Universal (CC0 1.0) Public Domain Dedication
  25. To the extent possible under law, the authors of this document have waived all copyright and related or neighboring rights to this work.