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

What to do about the integration list in the README #551

Closed
KodrAus opened this issue Apr 10, 2023 · 6 comments
Closed

What to do about the integration list in the README #551

KodrAus opened this issue Apr 10, 2023 · 6 comments

Comments

@KodrAus
Copy link
Contributor

KodrAus commented Apr 10, 2023

In #548 (comment) @JohnTitor brought up the broader question of what to do with the list of integrations listed in the README. They're currently presented as "the most popular" implementations out there. Right now the list isn't really curated that way; if there's a new crate that integrates with log then we add it to the list.

The function the list serves is giving users a kick-start to get actual data out of log, which on its own simply pipes your events into oblivion.

Alternative strategies to achieving that function are:

  • Linking a Cargo keyword for log or logger as mentioned in the linked comment.
  • Updating the wording of the README to not suggest the list is curated in any way besides listing libraries that integrate with log. It's up to end-users to evaluate the suitability of these libraries for their own needs.
@NobodyXu
Copy link

Would it be a good idea to mention tracing_log in the list, for it enables forwarding tracing to log or visa versa?

@KodrAus
Copy link
Contributor Author

KodrAus commented Apr 11, 2023

@NobodyXu Definitely 👍 It's a bit surprising we don't mention tracing at all in there.

@Thomasdezeeuw
Copy link
Collaborator

Maybe we should just change the wording? For example from:

There are many available implementations to choose from, here are some of the most popular ones:

To:

There are many available implementations to choose from, here are some options:

@KodrAus
Copy link
Contributor Author

KodrAus commented Apr 11, 2023

@Thomasdezeeuw that sounds good to me.

EFanZh pushed a commit to EFanZh/log that referenced this issue Jul 23, 2023
* Create universal binary for MacOS in workflow build
* Update README

Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>
@Thomasdezeeuw
Copy link
Collaborator

@KodrAus any further changes we want to make?

@KodrAus
Copy link
Contributor Author

KodrAus commented Jun 17, 2024

@Thomasdezeeuw I think it's all ok now. Are you happy for this issue to be closed?

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

3 participants