mirror of
https://codeberg.org/fediverse/fep.git
synced 2026-08-06 04:05:53 +00:00
repair incorrect issue url
This commit is contained in:
@@ -32,11 +32,10 @@ The FEP Process is an initiative of the [SocialHub](https://socialhub.activitypu
|
||||
| [FEP-5bf0: Collection sorting and filtering](./fep/5bf0/fep-5bf0.md) | `DRAFT` | [#80](https://codeberg.org/fediverse/fep/issues/80) | 2023-04-10 | - |
|
||||
| [FEP-888d: Using https://w3id.org/fep as a base for FEP-specific namespaces](./fep/888d/fep-888d.md) | `DRAFT` | [#83](https://codeberg.org/fediverse/fep/issues/83) | 2023-04-11 | - |
|
||||
| [FEP-0ea0: Payment Links](./fep/0ea0/fep-0ea0.md) | `DRAFT` | [#88](https://codeberg.org/fediverse/fep/issues/88) | 2023-04-18 | - |
|
||||
| [FEP-612d: Identifying ActivityPub Objects through DNS ](./fep/612d/fep-612d.md) | `DRAFT` | [#89](https://codeberg.org/fediverse/fep/issues/89) | 2023-04-18 | - |
|
||||
| [FEP-612d: Identifying ActivityPub Objects through DNS](./fep/612d/fep-612d.md) | `DRAFT` | [#89](https://codeberg.org/fediverse/fep/issues/89) | 2023-04-18 | - |
|
||||
| [FEP-fffd: Proxy Objects](./fep/fffd/fep-fffd.md) | `DRAFT` | [#95](https://codeberg.org/fediverse/fep/issues/95) | 2023-04-29 | - |
|
||||
| [FEP-4adb: Dereferencing identifiers with webfinger](./fep/4adb/fep-4adb.md) | `DRAFT` | [#100](https://codeberg.org/fediverse/fep/issues/100) | 2023-05-13 | - |
|
||||
| [FEP-a070: Ordered properties for plain JSON consumers](./fep/a070/fep-a070.md) | `DRAFT` | [#121](https://codeberg.org/api/v1/repos/fediverse/fep/issues/121) | 2023-06-13 | - |
|
||||
|
||||
| [FEP-a070: Ordered properties for plain JSON consumers](./fep/a070/fep-a070.md) | `DRAFT` | [#121](https://codeberg.org/fediverse/fep/issues/121) | 2023-06-13 | - |
|
||||
|
||||
## Submitting a FEP
|
||||
|
||||
@@ -47,10 +46,12 @@ To create and submit a FEP:
|
||||
1. Fork this repository, and then clone it to your local machine. Check the Codeberg [Cheat sheet](https://docs.codeberg.org/collaborating/pull-requests-and-git-flow/#cheat-sheet) on how to prepare your Pull Request.
|
||||
2. Think of a title for the FEP you want to submit.
|
||||
3. 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
|
||||
```
|
||||
|
||||
4. Create a subdirectory of `fep/`(fep/) using the identifier you just computed. Copy the FEP template ([fep-xxxx-template.md](./fep-xxxx-template.md)) to this subdirectory and change the filename appropriately. Use the identifer as the "slug" when filling out the frontmatter. For example, if your computed identifier was `abcd`, then your file would be located at `fep/abcd/fep-abcd.md` and your frontmatter would include `slug: "abcd"`.
|
||||
5. Write down your idea in the newly created file and commit it to a new branch in your repository (ex. fep-xxxx).
|
||||
6. Create a Pull Request to complete Step 1 of [FEP-a4ed: The Fediverse Enhancement Proposal Process](./feps/fep-a4ed.md). Further process is described in FEP-a4ed.
|
||||
@@ -65,6 +66,6 @@ Do you have ideas to improve the FEP Process? Post your suggestions to the issue
|
||||
|
||||
## License
|
||||
|
||||
CC0 1.0 Universal (CC0 1.0) Public Domain Dedication
|
||||
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.
|
||||
|
||||
@@ -3,7 +3,7 @@ slug: "a070"
|
||||
authors: a <a@trwnh.com>
|
||||
status: DRAFT
|
||||
dateReceived: 2023-06-13
|
||||
discussionsTo: https://codeberg.org/api/v1/repos/fediverse/fep/issues/121
|
||||
discussionsTo: https://codeberg.org/fediverse/fep/issues/121
|
||||
---
|
||||
# FEP-a070: Ordered properties for plain JSON consumers
|
||||
|
||||
|
||||
Reference in New Issue
Block a user