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

Move non-core instrumentations/exporters/propagators out of main repo #1233

Closed
codeboten opened this issue Oct 13, 2020 · 3 comments · Fixed by #1258
Closed

Move non-core instrumentations/exporters/propagators out of main repo #1233

codeboten opened this issue Oct 13, 2020 · 3 comments · Fixed by #1258
Assignees

Comments

@codeboten
Copy link
Contributor

As per discussion in the SIG meetings, we want to move all non-core instrumentations/exporters and propagators out of this repo and into the opentelemetry-python-contrib repo.

Benefits

  • less area to cover in the core repo
  • accelerate merging of third-party instrumentations/exporters/propagators

Goals

  • CI pipeline somehow must remain sane: validation that PRs in either repo isn't breaking the other repo
    if a new release of otel-py is out, the contrib repo should be updated
  • maintain contributors history
  • releasing package in contrib should be easier: currently every package depends on all the other ones being released, this means releases are slower
  • identify maintainers/approvers
  • determine the guidelines for approving/merging/releasing
@NathanielRN
Copy link
Contributor

Thanks for writing this up, @codeboten! Looking forward to helping 👍

@Oberon00
Copy link
Member

Oberon00 commented Oct 30, 2020

I just noticed running python scripts/eachdist.py lint takes extremely long (6 minutes on my rather fast 12 logical core notbook, using all cores) because pylint is not exactly fast. There are lots of packages and I think there is no ready-made support to exclude something from the script.

@codeboten
Copy link
Contributor Author

Closing this for now. Thanks for all the work @NathanielRN!

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 a pull request may close this issue.

3 participants