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

Proposal: Introduce OTEP Implementation Status #4322

Open
yurishkuro opened this issue Dec 5, 2024 · 4 comments
Open

Proposal: Introduce OTEP Implementation Status #4322

yurishkuro opened this issue Dec 5, 2024 · 4 comments
Labels
spec:miscellaneous For issues that don't match any other spec label triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor

Comments

@yurishkuro
Copy link
Member

Problem

OTEP 170 has been accepted 3yrs ago. But it is unclear which parts of it, if any, have been implemented in the Specification.

Proposal

Add a mandatory "Implementation Status" field to OTEP's metadata, placed at the top of the OTEP document (below the title). Valid status values:

  • not implemented - none of the proposals of the OTEP have been transferred to the Spec
  • partially implemented - some of the proposed changes have been applied. A bullet list of included / not included changes should be surfaced. A link to the implementation PR(s) should be included.
  • fully implemented - all proposals from the OTEP have been implemented in the Spec. A link to the implementation PR(s) should be included.
@yurishkuro yurishkuro added the spec:miscellaneous For issues that don't match any other spec label label Dec 5, 2024
@svrnm svrnm added the triage:deciding:tc-inbox Needs attention from the TC in order to move forward label Dec 9, 2024
@reyang
Copy link
Member

reyang commented Dec 11, 2024

We discussed this during the Dec. 11th, 2024 TC meeting. Tracking status is good, we suggest:

  1. Have a central place tracking the status, similar to the spec compliance matrix doc.
  2. Put the link in all the OTEP documents so the reader can find the status.

@reyang reyang added triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor and removed triage:deciding:tc-inbox Needs attention from the TC in order to move forward labels Dec 11, 2024
@reyang
Copy link
Member

reyang commented Dec 11, 2024

@yurishkuro would you want to be a sponsor?

@yurishkuro
Copy link
Member Author

Have a central place tracking the status, similar to the spec compliance matrix doc.

I think this would be an overhead that is not worth it. I would define status directly in the OTEP, because that's where I needed it when I am looking back at an OTEP.

We could then grep the OTEPs and generate a summary table if that's desired.

@yurishkuro
Copy link
Member Author

would you want to be a sponsor?

@reyang yes, I can be

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec:miscellaneous For issues that don't match any other spec label triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
Projects
Status: No status
Development

No branches or pull requests

3 participants