ActivityPubDev
/
Fediverse-Enhancement-Proposals
3
1
Fork 6
Code Issues 3 Pull Requests 0 Releases 0 Wiki Activity
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.
42 Commits
2 Branches
213 KiB
 
Branch: main
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'main'
${ noResults }
 ZIP  TAR.GZ
pukkamustard 64cc44005f Receive FEP-400e. 2 months ago
ISSUE_TEMPLATE ISSUE_TEMPLATE/tracking_issue.md: Add template for tracking issue 4 months ago
feps Receive FEP-400e. 2 months ago
EDITORS.md Add cjslep's Mastodon handle to EDITORS.md 5 months ago
LICENSE init 7 months ago
README.md Receive FEP-400e. 2 months ago
SUBMISSION.md EDITORS -> EDITORS.md and SUBMISSION_METHODS -> SUBMISSION.md 5 months ago
fep-0000-template.md FEP-a4ed: Draft updates 5 months ago

README.md

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 syncrhonization across servers DRAFT #11 2020-10-24 -
FEP-f1d5: NodeInfo in Fediverse Software DRAFT #12 2020-12-13 -
FEP-400e: Publicly-appendable ActivityPub collections DRAFT #17 2021-02-16 -

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.