forked from TrueCloudLab/frostfs.info
Stanislav Bogatyrev
01d465cb33
The FEP-1 describes what FEPs are and process around them. Signed-off-by: Stanislav Bogatyrev <s.bogatyrev@yadro.com>
1.2 KiB
1.2 KiB
| title | icon | description | type | date |
|---|---|---|---|---|
| FrostFS Proposals | ti-blackboard | Index of FrostFS Enhancement Proposals | docs | 2022-12-22 |
Introduction
FrostFS Enhancement Proposals (FEPs) describe standards for the whole FrostFS stack, including core protocol, API specification and services behavior.
Proposals numbers are assigned by the proposals editors, and once assigned are never changed.
To learn more about the purpose of FEPs and how to go about writing one, please refer to [FEP-1]({{< ref "/proposals/proc/fep-0001" >}}).
FEP Status Key
- Accepted — Normative proposal accepted for implementation
- Active — Currently valid informational guidance, or an in-use process
- Deferred — Inactive draft that may be taken up again at a later time
- Draft — Proposal under active discussion and revision
- Final — Accepted and implementation complete, or no longer active
- Provisional — Provisionally accepted but additional feedback needed
- Rejected — Formally declined and will not be accepted
- Superseded — Replaced by another succeeding FEP
- Withdrawn — Removed from consideration by sponsor or authors