-
Notifications
You must be signed in to change notification settings - Fork 303
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
Add Deprecated status to SEP Process #388
Conversation
Create a deprecated status and explain how to move a SEP into it. Its important that we remove any cruft from our SEPs to ensure people have a clear understanding of the state of the ecosystem, and to prevent people from implementing SEPs that won't be compatible with anyone else.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple comments 💬 .
ecosystem/README.md
Outdated
@@ -10,6 +10,7 @@ | |||
and it requires approval by 2 SDF members of the SEP Team. | |||
|
|||
## SEP Status Terms | |||
* **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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should move this into the Additional Statuses
section. The statuses in the SEP Status Terms
section are for proposals that are accepted or on track for being accepted. The statuses in the Additional Statuses
appear to be for proposals that are no longer in use, which a deprecated proposal is more related.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree: this should move to Additional Statuses
. The current Status Terms
list is in order of evolution from Draft through Final.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than one minor suggested change, this looks great.
ecosystem/README.md
Outdated
@@ -10,6 +10,7 @@ | |||
and it requires approval by 2 SDF members of the SEP Team. | |||
|
|||
## SEP Status Terms | |||
* **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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree: this should move to Additional Statuses
. The current Status Terms
list is in order of evolution from Draft through Final.
Create a deprecated status and explain how to move a SEP into it. Its important that we remove any cruft from our SEPs to ensure people have a clear understanding of the state of the ecosystem, and to prevent people from implementing SEPs that won't be compatible with anyone else.