-
Notifications
You must be signed in to change notification settings - Fork 974
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
List external ressources / tutorials on rust-libp2p #5717
Comments
Thank you for bringing up the topic of external resources for rust-libp2p. I completely agree that well-curated external resources can be incredibly valuable for newcomers and even experienced developers looking to deepen their understanding of peer-to-peer networking with Rust. Resources like tutorials and live coding sessions often provide practical insights and step-by-step guidance that can complement our official documentation and examples. Wish to suggest some more external resources, which we may include:
|
As discussed in yesterday's libp2p Community Call and recent maintainer's call, I'd like to share some feedback and thoughts on including external resources to scale developer adoption: Pros of Including External Resources: Managing the Risk of Outdated Content: Recommended Curation Strategy:
Adding an External Resources section to examples/README.md can enhance the onboarding experience and provide valuable learning paths for developers. By implementing periodic reviews, clear disclaimers, and community-driven curation, we can mitigate the risk of outdated content while maximizing the value of these resources. Thoughts and further input are welcome :) |
In the last community call, the topic of external resources on (rust-)libp2p came up.
There are quite a few useful ones out there, e.g.:
I wanted to open the discussion on whether we want do include links to such resources in our repo, e.g. in as a
## External Resources
section in ourexamples/README.md
.I think they can help newcomers quite a bit.
However, because they are external, there is also the risk of them being or becoming outdated and not working with our current API anymore.
The text was updated successfully, but these errors were encountered: