Skip to content
This repository has been archived by the owner on Jul 21, 2023. It is now read-only.

Handle remaining TODOs #14

Open
daviddias opened this issue Aug 26, 2017 · 2 comments
Open

Handle remaining TODOs #14

daviddias opened this issue Aug 26, 2017 · 2 comments
Labels
exp/expert Having worked on the specific codebase is important P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked

Comments

@daviddias
Copy link
Member

#1
@daviddias daviddias changed the title Handle remaining TODO Handle remaining TODOs Aug 26, 2017
@daviddias daviddias added status/ready Ready to be worked help wanted Seeking public contribution on this issue exp/expert Having worked on the specific codebase is important P1 High: Likely tackled by core team if no one steps up labels Feb 5, 2018
@zcstarr
Copy link

zcstarr commented Feb 23, 2018

@diasdavid I'd like to jump in if there are any issues that can be picked off from the overarching dht awesomeness arc.

@daviddias daviddias removed the help wanted Seeking public contribution on this issue label Feb 26, 2018
@daviddias
Copy link
Member Author

Thank you, @zcstarr :) I'm currently moving things around, tracked -- libp2p/js-libp2p#159 --. Given that you are new to the project, it would be good to get you started on some of the quicker (difficulty:easy) help wanted labeled issues on js-libp2p, so that you are comfortable around the module codebase. Check which issues have both labels and are ready to be worked on at https://waffle.io/libp2p/js-libp2p

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
exp/expert Having worked on the specific codebase is important P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zcstarr @daviddias