mirrors/fep
1
0
Fork 0
mirror of https://codeberg.org/fediverse/fep.git synced 2026-08-05 19:55:46 +00:00
Code Packages Wiki Activity

Merge pull request 'FEP-a4ed: Updates 3' (#13) from pukkamustard/Fediverse-Enhancement-Proposals:list-in-readme into main

Browse Source 
Reviewed-on: https://git.activitypub.dev/ActivityPubDev/Fediverse-Enhancement-Proposals/pulls/13
Reviewed-by: cjslep <cjslep@gmail.com>
This commit is contained in:
pukkamustard
2021-01-04 15:29:28 +00:00
parent db519b1329 dc1c4e208d
commit 49e1412b89
3 changed files with 29 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ISSUE_TEMPLATE/tracking_issue.md
+16
View File
@@ -0,0 +1,16 @@
---
name: "FEP Tracking Issue"
about: "This template is for creating a tracking issue for a newly received FEP"
title: "[TRACKING] FEP-XXX: TITLE "
---
The proposal has been received. Thank you!
This issue tracks discussions and updates to the proposal during the `DRAFT` period.
Please post links to relevant discussions as comment to this issue.
`dateReceived`: [DATE-RECEIVED]
If no further actions are taken, the proposal will be automatically set to `WITHDRAWN` on [DATE-RECEIVED+120-DAYS] (in 120 days).
README.md
+12 -2
View File
@@ -4,6 +4,16 @@ 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
<!-- TODO: This table is not CommonMark (as specified by FEP-a4ed) and requires maintenance. It should be replaced by a dynamically created table. -->
| Title | Status | Tracking issue | `dateReceived` | `dateFinalized` (or `dateWithdrawn`) |
| --- | --- | ----- | ------- | ------ |
| [FEP-a4ed: The Fediverse Enhancement Proposal Process](./feps/fep-a4ed.md) | `DRAFT` | [#10](https://git.activitypub.dev/ActivityPubDev/Fediverse-Enhancement-Proposals/issues/10) | 2020-10-16 | - |
| [FEP-8fcf: Followers collection syncrhonization across servers](./feps/fep-8fcf.md) | `DRAFT` | [#11](https://git.activitypub.dev/ActivityPubDev/Fediverse-Enhancement-Proposals/issues/11) | 2020-10-24 | - |
| [FEP-f1d5: NodeInfo in Fediverse Software](./feps/fep-f1d5.md) | `DRAFT` | [#12](https://git.activitypub.dev/ActivityPubDev/Fediverse-Enhancement-Proposals/issues/12) | 2020-12-13 | - |
# 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).
@@ -20,8 +30,8 @@ b3f0
3. Copy the FEP template ([fep-0000-template.md](./fep-0000-template.md)) to the [feps/](feps/) folder and change the filename to `fep-abcd.md` where `abcd` is the identifier computed in step 2.
4. Write down your idea in the newly created file.
5. Submit a Pull Request to this repository containing your proposal (other submission methods may be listed in [`SUBMISSION.md`](./SUBMISSION.md)).
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`.
7. You (as author) are now responsible for initiating community discussion and collecting feedback. While the proposal is in status `DRAFT` you may submit changes to the proposal via Pull Requests.
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`. The editors will also create a tracking issue for your proposal.
7. 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).
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 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](./feps/fep-a4ed.md).
feps/fep-a4ed.md
+1 -1
View File
@@ -105,7 +105,7 @@ Fediverse Enhancement Proposals must be placed in the public domain by the autho
- Authors may withdraw the submission upon which an editor will set the status of the submission to `WITHDRAWN`.
5. After at least 60 days the authors may request the proposal to be finalized. This is done by requesting final comments on the proposal.
- If there are no community objections within 14 days and the authors can show that they have initiated sufficient awareness and discussion of the proposal, an editor will set the status of the submission to `FINAL`.
6. If after 90 days the authors have not requested the proposal to be finalized or there is no community consensus, an editor will set the status of the submission to `WITHDRAWN`.
6. If after 120 days the authors have not requested the proposal to be finalized or there is no community consensus, an editor will set the status of the submission to `WITHDRAWN`.
7. A proposal with status `FINAL` can not be changed or updated.
8. A proposal with status `WITHDRAWN` remains in the repository and can be resubmitted.