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

Awesome Endeavor: Libp2p Core Documentation #308

Closed
jacobheun opened this issue Jan 15, 2019 · 3 comments
Closed

Awesome Endeavor: Libp2p Core Documentation #308

jacobheun opened this issue Jan 15, 2019 · 3 comments
Labels
dx Developer Experience exp/novice Someone with a little familiarity can pick up help wanted Seeking public contribution on this issue kind/bug A bug in existing code (including security flaws) P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked

Comments

@jacobheun
Copy link
Contributor

jacobheun commented Jan 15, 2019

One of our goals for this quarter, is to audit the libp2p core modules and ensure the docs and examples are up to date and that they exist; Q1 2019 OKR.

The following table will be used to track the status of documentation across the core modules of libp2p. Some modules may have adequate examples and the README may already be up to date, but this will allow us to appropriately audit those. If examples do exist, they should be audited for correctness, and we should ensure they are running properly.

Note, some of the packages below may be very low priority, due to either pending deprecation or the module is not yet released.

All contributions are welcome! Let us know if you have questions, and fill free to claim a module by commenting :)

  • 🍎= Not started
  • 🍋= Very low priority
  • 🍊= In progress
  • 🍏= Complete
Status Package Owner
🍊 js-libp2p-interfaces
🍊 js-libp2p
🍅 js-libp2p-bootstrap
🍅 js-libp2p-crypto
🍅 js-libp2p-crypto-secp256k1
🍅 js-libp2p-delegated-content-routing
🍅 js-libp2p-delegated-peer-routing
🍅 js-libp2p-floodsub
🍅 js-libp2p-kad-dht
🍅 js-libp2p-mdns
🍅 js-libp2p-mplex
🍅 js-libp2p-record
🍊 js-libp2p-rendezvous
🍅 js-libp2p-tcp
🍋 js-libp2p-webrtc-star
🍋 js-libp2p-webrtc-direct
🍋 js-libp2p-websockets
🍅 js-peer-id
@jacobheun jacobheun added kind/bug A bug in existing code (including security flaws) help wanted Seeking public contribution on this issue exp/novice Someone with a little familiarity can pick up status/ready Ready to be worked P2 Medium: Good to have, but can wait until someone steps up labels Jan 15, 2019
@jacobheun jacobheun added the dx Developer Experience label Apr 8, 2019
@jacobheun jacobheun pinned this issue Apr 8, 2019
@jacobheun
Copy link
Contributor Author

Module: js-libp2p
Related Issues: #231, #237, #350

For js-libp2p we need to audit, improve and standardize on our language. Once we've done that we should ensure, as a part of this effort, that the other libp2p modules conform to that.

@jacobheun jacobheun added P1 High: Likely tackled by core team if no one steps up and removed P2 Medium: Good to have, but can wait until someone steps up labels Apr 8, 2019
@vasco-santos
Copy link
Member

We should revisit this issue after the next release, as things are now much better :D

@maschad
Copy link
Member

maschad commented Oct 1, 2023

Closing due to staleness

@maschad maschad closed this as completed Oct 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dx Developer Experience exp/novice Someone with a little familiarity can pick up help wanted Seeking public contribution on this issue kind/bug A bug in existing code (including security flaws) P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked
Projects
None yet
Development

No branches or pull requests

4 participants