Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the definitions of Active and Final status #389

Merged
merged 4 commits into from
Sep 3, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
26 changes: 14 additions & 12 deletions ecosystem/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,14 +15,10 @@
Team. If enough the approval requirements are met by SEP team members, the SEP will move towards
`FCP`. Otherwise, it'll regress to a `Draft`.
* **FCP** — A SEP that has entered a Final Comment Period (FCP). After one week has passed, during
which any new concerns should be addressed, the SEP's status will become `Active` or `Final`,
depending on the content of the SEP.
which any new concerns should be addressed, the SEP's status will become `Active`.
* **Active** - An actively maintained SEP that is intended for immediate adoption by the entire
ecosystem by its author(s), and if it is a Standard, by SDF as well. Additional updates may be
made without changing the SEP number.
* **Final** - A finalized SEP that is intended for immediate adoption by the entire
ecosystem by its author(s), and if it is a Standard, by SDF as well. A final SEP should only be
updated to correct errata.
ecosystem. Additional updates may be made without changing the SEP number.
* **Final** - A finalized SEP will not be changed aside from minor errata. For a proposal to be a candidate to be made Final it must be being used in live products.

### Additional Statuses
* **Deprecated** - A SEP that was previously on an active track but has been deprecated and is no longer suggested for use. There may be legacy usage of a deprecated SEP.
Expand Down Expand Up @@ -143,11 +139,17 @@ From there, the following process will happen:
* Once a SEP has been approved, it goes into FCP which is broadcast to the protocol meeting members
along with the mailing list.

### FCP -> Active/Final
* If no major concerns are brought up, the SEP is marked as `Active` or `Final` by your SEP buddy:
* If the SEP requires active maintenance, such as having an open schema, it should be marked at
`Active`.
* Otherwise, the SEP should be marked as `Final`.
### FCP -> Active
* If no major concerns are brought up, the SEP is marked as `Active` by your SEP buddy.
* Ideally there will be a reference implementation exhibiting the behavior and value of the SEP before moving to active state.
* Active SEPs should be brought into production by ecosystem members.
* Minor changes may be made as more implementations are brought online highlighting any edge cases.

### Active -> Final
* Once the SEP team determines that an active SEP is complete, proven, and won't be extended, the SEP can move to `Final` status.
* This promotion can only occur once there are multiple live implementations being used in production to ensure any edge cases or incompatibilities are found.
* No changes will be made to a finalized SEP aside from fixing minor errata.
* Much consideration should be given before moving to Final status, it is OK for SEPs to live in Active status for a long time.

### Regression
* It is possible for a SEP to move from `Active` to `Draft` or `Deprecated` if it is never adopted, or is abandoned by the community.
Expand Down