Skip to content

Commit c7bbbe9

Browse files
Clarify OTEPs are documents of intent. (#4308)
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?
1 parent ca2a0d4 commit c7bbbe9

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

oteps/README.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,10 @@
44

55
OpenTelemetry uses an "OTEP" (similar to a RFC) process for proposing changes to the OpenTelemetry Specification.
66

7+
> [!NOTE]
8+
> OTEPs are documents of intent. They become requirements only after their contents have been
9+
> [integrated](#integrating-the-otep-into-the-spec) into the actual [Specification](../specification).
10+
711
### Table of Contents
812

913
- [OpenTelemetry Enhancement Proposal (OTEP)](#opentelemetry-enhancement-proposal-otep)

0 commit comments

Comments
 (0)