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

OEP-37 Dev Data: Evaluate whether to carry this forward or not. #607

Open
Tracked by #573
sarina opened this issue Jul 5, 2024 · 0 comments
Open
Tracked by #573

OEP-37 Dev Data: Evaluate whether to carry this forward or not. #607

sarina opened this issue Jul 5, 2024 · 0 comments
Labels
help wanted Ready to be picked up by anyone in the community

Comments

@sarina
Copy link
Contributor

sarina commented Jul 5, 2024

Several OEPs were authored aspirationally, and then never implemented. Other were partially implemented, but have stalled or diverged from reality.

In order to establish OEPs as a trustworthy source of documentation, we should mark OEPs that never came to be as "Replaced" or "Obsolete" (whichever or is more appropriate). We should amend OEPs that are still relevant but mismatched with reality.

OEP-37 is one of these, as called out in #573

@sarina sarina added the help wanted Ready to be picked up by anyone in the community label Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Ready to be picked up by anyone in the community
Projects
None yet
Development

No branches or pull requests

1 participant