Skip to content
This repository has been archived by the owner on Dec 6, 2024. It is now read-only.

Rename the repo to "otrfcs"? #2

Closed
bogdandrutu opened this issue Jun 25, 2019 · 6 comments
Closed

Rename the repo to "otrfcs"? #2

bogdandrutu opened this issue Jun 25, 2019 · 6 comments

Comments

@bogdandrutu
Copy link
Member

No description provided.

@iredelmeier
Copy link
Member

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?

@bogdandrutu
Copy link
Member Author

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.

@ernado
Copy link

ernado commented Aug 17, 2019

Please do, collisions with IETF RFC are unnecessary.

Sadly, Rust has already done this:
https://github.com/rust-lang/rfcs

Currently, RFC 1234 is unambiguously referring to IETF (with expection to Rust), let's not make it more complicated.

@bogdandrutu
Copy link
Member Author

Based on the comments I think "oteps" is better. Please +1 or -1 for this proposal.

@bogdandrutu
Copy link
Member Author

Ok, I see no objections. I will go ahead and change this to "oteps" ("OpenTelemetry Enhancement Proposal")

@bogdandrutu
Copy link
Member Author

Done.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants