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

Consider to rename this to opentelemetry-specs? #2

Closed
bogdandrutu opened this issue May 2, 2019 · 7 comments
Closed

Consider to rename this to opentelemetry-specs? #2

bogdandrutu opened this issue May 2, 2019 · 7 comments

Comments

@bogdandrutu
Copy link
Member

Pros: Shorter

@iredelmeier
Copy link
Member

Alternatively, just specification?

@bogdandrutu
Copy link
Member Author

We had this argument before, if the name is too generic when people fork this repo will not make sense inside their account.

@iredelmeier
Copy link
Member

@bogdandrutu mind linking that discussion in here?

@bogdandrutu
Copy link
Member Author

/cc @yurishkuro

@austinlparker
Copy link
Member

austinlparker commented May 6, 2019

my 0.02 is that opentelemetry-specification is more explicit and preferable. additionally, it's a word that's highly unlikely to ever be overloaded (unlike the word spec/s, which could be used as a language or library name - i would point to spec# or the spec package in npm as examples of this.) not to say no one would ever name a language/package specification`, but it feels a bit more reserved.

@yurishkuro
Copy link
Member

My preference, in the decreasing order:

  1. close this issue as bikeshedding
  2. specification
  3. opentelemetry-specification

@austinlparker
Copy link
Member

Closing as bikeshedding.

rockb1017 pushed a commit to rockb1017/opentelemetry-specification that referenced this issue Nov 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants