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

fix(roadmap): correct table formatting #4100

Merged
merged 1 commit into from
Jun 22, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 12 additions & 12 deletions ROADMAP.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ Implement the new AutoNAT v2 specification. See https://github.com/libp2p/specs/
## Optimize Hole punching

| Category | Status | Target Completion | Tracking | Dependencies | Dependents |
|--------------+--------+-------------------+----------+--------------+------------|
|--------------|--------|-------------------|----------|--------------|------------|
| Optimization | todo | | | | |

We released hole punching support with [rust-libp2p
Expand All @@ -58,7 +58,7 @@ hole punching stack.
## Improved Wasm support

| Category | Status | Target Completion | Tracking | Dependencies | Dependents |
|----------------------+--------+-------------------+---------------------------------------------------+--------------+----------------------------------------------|
|----------------------|--------|-------------------|---------------------------------------------------|--------------|----------------------------------------------|
| Developer ergonomics | todo | | https://github.com/libp2p/rust-libp2p/issues/2617 | | [WebRTC](#webrtc-support-browser-to-browser) |

The project supports Wasm already today, though the developer experience is cumbersome at best.
Expand All @@ -70,7 +70,7 @@ argue that that demand follows this roadmap item and not the other way round.)
## WebRTC in the browser via WASM

| Category | Status | Target Completion | Tracking | Dependencies | Dependents |
|--------------+--------+-------------------+--------------------------------------------+-------------------------------------------------------------------------------------------+------------|
|--------------|--------|-------------------|--------------------------------------------|-------------------------------------------------------------------------------------------|------------|
| Connectivity | todo | | https://github.com/libp2p/specs/issues/475 | [Improved WASM support](#improved-wasm-support), https://github.com/libp2p/specs/pull/497 | |

Use the browser's WebRTC stack to support
Expand Down Expand Up @@ -114,8 +114,8 @@ https://github.com/libp2p/rust-libp2p/pull/2289.

### WebRTC support (browser-to-server)

| Category | Status | Target Completion | Tracking | Dependencies | Dependents |
|--------------|--------|-------------------|------------------------------------------|------------------------------------------------|-------------------------------------------------------------------|
| Category | Status | Target Completion | Tracking | Dependencies | Dependents |
|--------------|--------|-------------------|------------------------------------------|-----------------------------------------------|-------------------------------------------------------------------|
| Connectivity | Done | Q4/2022 | https://github.com/libp2p/specs/pull/412 | https://github.com/libp2p/test-plans/pull/100 | [WebRTC (browser-to-browser)](#webrtc-support-browser-to-browser) |

We are currently implementing WebRTC for **browser-to-server** connectivity in
Expand All @@ -138,9 +138,9 @@ work before that.

### Generic connection management

| Category | Status | Target Completion | Tracking | Dependencies | Dependents |
|----------------------|-------------|-------------------|---------------------------------------------------|--------------|------------|
| Developer Ergonomics | done | Q1/2023 | https://github.com/libp2p/rust-libp2p/issues/2824 | | |
| Category | Status | Target Completion | Tracking | Dependencies | Dependents |
|----------------------|--------|-------------------|---------------------------------------------------|--------------|------------|
| Developer Ergonomics | done | Q1/2023 | https://github.com/libp2p/rust-libp2p/issues/2824 | | |

Today connection management functionality in rust-libp2p is limited. Building abstractions on top is
cumbersome and inefficient. See https://github.com/libp2p/rust-libp2p/issues/2824. Making connection
Expand Down Expand Up @@ -174,9 +174,9 @@ QUIC](https://github.com/libp2p/specs/blob/master/relay/DCUtR.md#the-protocol).

## Kademlia client mode

| Category | Status | Target Completion | Tracking | Dependencies | Dependents |
|--------------|-------------|-------------------|---------------------------------------------------|-----------------------------------------------------------------|------------|
| Optimization | Done | Q2/2023 | https://github.com/libp2p/rust-libp2p/issues/2032 | [Cross behaviour communication](#cross-behaviour-communication) | |
| Category | Status | Target Completion | Tracking | Dependencies | Dependents |
|--------------|--------|-------------------|---------------------------------------------------|-----------------------------------------------------------------|------------|
| Optimization | Done | Q2/2023 | https://github.com/libp2p/rust-libp2p/issues/2032 | [Cross behaviour communication](#cross-behaviour-communication) | |

Kademlia client mode will enhance routing table health and thus have a positive impact on all
Kademlia operations.
Kademlia operations.