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

Document instrumentation hosting recommendations. #1100

Closed
MrAlias opened this issue Sep 13, 2021 · 1 comment · Fixed by #1103
Closed

Document instrumentation hosting recommendations. #1100

MrAlias opened this issue Sep 13, 2021 · 1 comment · Fixed by #1103
Assignees
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@MrAlias
Copy link
Contributor

MrAlias commented Sep 13, 2021

The size of the developer community supporting this project is not large enough to support the ever growing amount of instrumentation being submitted to this repository. We need to document instrumentation guidelines discussed in last week's SIG meeting that address this with the following prioritization of where instrumentation should be hosted:

  1. Native to any package. Instrumentation exists in the package itself.
  2. Hosted by the maintainer in their own public git repository. List it in the opentelemetry.io registry.
  3. Hosted by OTel in contrib. We need to document when this is warranted and what the process will be to submit.
@MrAlias MrAlias added the documentation Improvements or additions to documentation label Sep 13, 2021
@MrAlias
Copy link
Contributor Author

MrAlias commented Sep 13, 2021

As a follow on to documenting the project policy, we need to close outstanding PRs here for instrumentation we will not be accepting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants