-
Notifications
You must be signed in to change notification settings - Fork 164
Rename the repo to "otrfcs"? #2
Comments
For more context, there have been similar discussions for other repos with "common" names, e.g., in community and in opentelemetry-specification. For RFCs specifically, we could also do something like rename them from RFCs to OTEPs (for "OpenTelemetry Enhancement Proposal"), à la Python's PEPs and Kubernetes's KEPs. Thoughts? |
RFCs sounds like standards and I know there is a push from CNCF to not define standards. If we scope the rfc to OpenTelemetry should be fine that's the main reason. |
Please do, collisions with IETF RFC are unnecessary. Sadly, Rust has already done this: Currently, RFC 1234 is unambiguously referring to IETF (with expection to Rust), let's not make it more complicated. |
Based on the comments I think "oteps" is better. Please +1 or -1 for this proposal. |
Ok, I see no objections. I will go ahead and change this to "oteps" ("OpenTelemetry Enhancement Proposal") |
Done. |
No description provided.
The text was updated successfully, but these errors were encountered: