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

Propose that we move OTEPs into the specification repository. #266

Merged
merged 6 commits into from
Oct 22, 2024

Conversation

jsuereth
Copy link
Contributor

No description provided.

text/0266-move-oteps-to-spec.md Show resolved Hide resolved
text/0266-move-oteps-to-spec.md Show resolved Hide resolved
text/0266-move-oteps-to-spec.md Show resolved Hide resolved
@jsuereth jsuereth marked this pull request as ready for review September 3, 2024 14:20
Copy link
Member

@dyladan dyladan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I support this idea, but would remove the text/ part of the directory path.

text/0266-move-oteps-to-spec.md Show resolved Hide resolved
text/0266-move-oteps-to-spec.md Show resolved Hide resolved
Copy link
Contributor

@pyohannes pyohannes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I appreciate the effort to reduce overhead, I just added a few questions about details.

text/0266-move-oteps-to-spec.md Show resolved Hide resolved
text/0266-move-oteps-to-spec.md Show resolved Hide resolved
@austinlparker
Copy link
Member

Just a note from the spec meeting today; We should ensure that when this move happens that we clarify the use of normative language in OTEPs (and where needed, ensure that existing OTEPs are normalized to that decision)

@jack-berg
Copy link
Member

@jsuereth do you have a plan / schedule in mind for merging and executing this plan?

@carlosalberto
Copy link
Contributor

We will merge this OTEP as it has enough approvals and will start the work, tuning further details, such as:

  • Retain git history
  • Issue migration
  • OTEP number assignation
  • Use of normative language (clarify the expectation, as we currently do not use it much here)
  • Other items.

@carlosalberto carlosalberto merged commit d1f73ee into open-telemetry:main Oct 22, 2024
4 checks passed
carlosalberto pushed a commit to carlosalberto/opentelemetry-specification that referenced this pull request Oct 31, 2024
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

Successfully merging this pull request may close these issues.