Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

docs: 2018 Q3 OKRs #207

Merged
merged 12 commits into from
Jul 4, 2018
5 changes: 4 additions & 1 deletion OKR.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,11 +12,14 @@ We try to frame our ongoing work using a process based on quarterly Objectives a
- IPNS works over PubSub (+ go-libp2p interop) - @vascosantos
- IPNS works over DHT (+ go-libp2p interop) - @vascosantos
Copy link
Member

@vasco-santos vasco-santos Jul 4, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IPNS is currently implemented in go-ipfs, so I think we should have go-ipfs interop for both IPNS KRs

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

You mean anything different from what is already there?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mean:

IPNS works over PubSub (+ go-ipfs interop) - @vascosantos
IPNS works over DHT (+ go-ipfs interop) - @vascosantos

Since IPNS is implemented inside the scope of js-ipfs / go-ipfs


**libp2p debugging is not painful**
**libp2p debugging and interop testing is not painful**

- Error handling is done correctly and error codes are part of the API - @jacobheun
- libp2p and libp2p-switch become full state machines - @jacobheun
- libp2p has a network visualization tool - @vascosantos
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@diasdavid you missed a hyphen on my handle 😛

- js-libp2p has a daemon with a RPC API and a client library
- We get the RPC API standardised so that go-libp2p and rust-libp2p can implement it as well
- Write the first set of interop tests that tests
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jacobheun how do you feel about adding and taking these. It would be pretty sweet and we would have the chance to model a lot of the things with regards to interop testing :)


**libp2p is seen as the go to p2p networking stack**

Expand Down