Clarify OTEPs are documents of intent. #4308
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
carlosalberto
force-pushed
the
oteps-intention-clarification
branch
from
9c258a8 to
7a1cff8
Compare
yurishkuro
approved these changes
Nov 20, 2024
MrAlias
approved these changes
Nov 20, 2024
reyang
approved these changes
Nov 20, 2024
lmolkova
approved these changes
Nov 21, 2024
pellared
approved these changes
Nov 21, 2024
jsuereth
approved these changes
Nov 21, 2024
arminru
approved these changes
Nov 21, 2024
arminru
added
the
editorial
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It was discussed, during the move of OTEPs to the Specification repo, that we want to let users know OTEPs are not part of the Specification until their contents have been actually integrated.
We had mentioned we may want to add this one to every OTEP. Any opinion?