List/link to third-party crates #373
Labels
Comments
|
More crates that should be linked:
|
hawkw
added a commit
that referenced
this issue
Jan 3, 2020
This branch adds a list of related crates not in this repository to the `tracing` RustDoc, the `tracing` README, and the root repository README. (cc @jonhoo, @jtescher, @pkinsky, @GregBowyer, @zanria, @hlb8122) Closes #373 Signed-off-by: Eliza Weisman <eliza@buoyant.io>
hawkw
added a commit
that referenced
this issue
Jan 4, 2020
* docs: add third-party crates to docs This branch adds a list of related crates not in this repository to the `tracing` RustDoc, the `tracing` README, and the root repository README. (cc @jonhoo, @jtescher, @pkinsky, @GregBowyer, @zanria, @hlb8122) Closes #373 Signed-off-by: Eliza Weisman <eliza@buoyant.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request
Motivation
I'm very pleased to note that there are now several crates in the ecosystem built on
tracingthat aren't part of this repository or maintained by me! Since these third-party crates aren't in this repository, however, they can be much less discoverable for users.Proposal
We should consider adding a list of external crates in the
tracingecosystem in the official documentation. This could be in the main README and/or somewhere in thetracingcrate's rustdoc.Some crates which should definitely be included:
tracing-timingby @jonhootracing-cozby @GregBowyertracing-actixby @zenriaAlternatives
Alternatively, if the authors of any of these crates are interested in having them become part of the
tracingproject officially, I'd be willing to talk about adding those crates to this repository and add their maintainers as code owners for those crates. However, for the most part, I don't think this is really necessary — I love seeing an ecosystem of external libraries; so unless the authors of external crates are particularly eager to see them merged in, I would be happy to continue with the current state of affairs.The text was updated successfully, but these errors were encountered: