Browse Source

Update ROADMAP-TO-1.0.0.md

David Dias 7 years ago
parent
commit
0439791c10
1 changed files with 32 additions and 32 deletions
  1. 32 32
      ROADMAP-TO-1.0.0.md

+ 32 - 32
ROADMAP-TO-1.0.0.md

@@ -51,7 +51,7 @@ These are some use case milestones to drive development.
   - [x] js-ipfs-api client inside a tab
   - [x] js-ipfs full node inside a tab
   - [x] browser extension gateway redirects
-  - [ ] browser extension full node
+  - [x] browser extension full node
   - [ ] impl native inside browsers
 - [x] Support for versioning and archival
   - [x] archival of files
@@ -117,7 +117,7 @@ These are some libraries that must exist to make developers' lives easy. It is c
   - [ ] ipfs api bindings in Erlang
 - [x] full ipfs node implementations
   - [x] go-ipfs - implementation in Go
-  - [ ] js-ipfs - implementation in JS
+  - [x] js-ipfs - implementation in JS
 - [x] developer libs for cli tools
 - [ ] developer libs for desktop apps
 - [x] developer libs for webapps
@@ -295,11 +295,11 @@ The libp2p protocols are the protocol stack for the modular p2p protocols librar
   - [ ] Stream Muxer: http2 in JS
   - [ ] Stream Muxer: QUIC in Go
   - [ ] Stream Muxer: QUIC in JS
-- [x] Swarm / Switch: interfaces
+- [x] Switch: interfaces
   - [x] Dialer stack in Go
   - [x] Dialer stack in JS
-  - [x] Swarm implementation in Go
-  - [x] Swarm implementation in JS
+  - [x] Switch implementation in Go
+  - [x] Switch implementation in JS
 - [x] NAT Traversal: interfaces
   - [x] nat-pmp implementation in Go
   - [ ] nat-pmp implementation in JS
@@ -438,7 +438,7 @@ The IPFS pub/sub service will provide fast delivery and routing for subnets of i
 - [ ] IPFS pub/sub: Protocol and architecture design
   - [ ] IPFS pub/sub: protocol spec / messages
   - [ ] IPFS pub/sub: record spec
-  - [ ] IPFS pub/sub: one-hop support
+  - [x] IPFS pub/sub: one-hop support
   - [ ] IPFS pub/sub: multihop tree forming
   - [ ] IPFS pub/sub: churn resistance
   - [ ] IPFS pub/sub: censor resistance
@@ -450,6 +450,7 @@ The IPFS pub/sub service will provide fast delivery and routing for subnets of i
 - [ ] IPFS pub/sub: impl in Go
   - [x] IPFS pub/sub: prototyping in Go
 - [ ] IPFS pub/sub: impl in JS
+  - [x] IPFS pub/sub: prototyping in JS
 - [ ] IPFS pub/sub: pssim simulations
   - [ ] IPFS pub/sub: pssim programmable config
   - [ ] IPFS pub/sub: pssim in-proc tests
@@ -519,14 +520,14 @@ IPLD data structures and importers are various data structures and programs that
     - [x] unixfs file sharding
     - [x] unixfs file trickledag
     - [x] unixfs dir
-    - [ ] unixfs dir sharding
+    - [x] unixfs dir sharding
     - [x] unixfs metadata
   - [x] unixfs impl in JS
     - [x] unixfs file
     - [x] unixfs file sharding
-    - [ ] unixfs file trickledag
+    - [x] unixfs file trickledag
     - [x] unixfs dir
-    - [ ] unixfs dir sharding
+    - [x] unixfs dir sharding
     - [x] unixfs metadata
 - [x] archives spec
   - [x] tar
@@ -674,16 +675,16 @@ The go-ipfs effort is the Go implementation of IPFS. It is meant to run as a com
 
 The js-ipfs effort is the javascript implementation of IPFS. It is meant to run on both node.js and today's regular web browsers. It is close, but not yet ready. More at https://github.com/ipfs/js-ipfs
 
-- [ ] js-ipfs ipfs node components
+- [x] js-ipfs ipfs node components
   - [x] js-ipfs multi protocols
   - [x] js-ipfs component: repo
   - [x] js-ipfs component: networking (libp2p)
   - [x] js-ipfs component: bitswap
   - [x] js-ipfs component: dag / ipld
-  - [ ] js-ipfs component: pinning
+  - [x] js-ipfs component: pinning
   - [x] js-ipfs component: block api
   - [x] js-ipfs component: object api
-  - [ ] js-ipfs component: files api
+  - [x] js-ipfs component: files api
   - [x] js-ipfs component: daemon
   - [x] js-ipfs component: data importing
   - [x] js-ipfs component: http api
@@ -696,13 +697,13 @@ The js-ipfs effort is the javascript implementation of IPFS. It is meant to run
     - [x] js-ipfs core api: object
     - [ ] js-ipfs core api: refs
     - [x] js-ipfs core api: repo
-    - [ ] js-ipfs core api: pin
+    - [x] js-ipfs core api: pin
     - [ ] js-ipfs core api: log
   - [ ] js-ipfs ext api impl
     - [ ] js-ipfs ext api: name (ipns)
     - [ ] js-ipfs ext api: dns
     - [ ] js-ipfs ext api: tar
-    - [ ] js-ipfs ext api: files
+    - [x] js-ipfs ext api: files
     - [ ] js-ipfs ext api: stat
     - [ ] js-ipfs ext api: mount
     - [x] js-ipfs ext api: bootstrap
@@ -713,15 +714,14 @@ The js-ipfs effort is the javascript implementation of IPFS. It is meant to run
     - [ ] js-ipfs tool api: update
     - [x] js-ipfs tool api: commands
   - [ ] js-ipfs net api impl
-    - [ ] js-ipfs net api: ping
+    - [x] js-ipfs net api: ping
     - [ ] js-ipfs net api: dht
-    - [ ] js-ipfs net api: swarm
-    - [ ] go-ipfs net api: records
-- [ ] js-ipfs cli api impl
-  - [ ] js-ipfs cli codecs
-- [ ] js-ipfs http api impl
-  - [ ] js-ipfs http api: streaming
-  - [ ] js-ipfs http api: multipart
+    - [x] js-ipfs net api: swarm
+    - [ ] js-ipfs net api: records
+- [x] js-ipfs cli api impl
+- [x] js-ipfs http api impl
+  - [x] js-ipfs http api: streaming
+  - [x] js-ipfs http api: multipart
 
 ### IPFS directly on the Browsers
 
@@ -738,18 +738,18 @@ We have finished step (1). We are currently working on steps (2) and (3). Step (
   - [x] go-ipfs implementation
   - [x] js-ipfs-api client library
   - [x] use background go-ipfs node (localhost or elsewhere)
-- [ ] IPFS protocol running in a browser tab, in js
+- [x] IPFS protocol running in a browser tab, in js
   - [x] js-libp2p implementation
-  - [ ] js-ipfs implementation
+  - [x] js-ipfs implementation
   - [x] libp2p.js browser library
-  - [ ] ipfs.js browser library
+  - [x] ipfs.js browser library
 - [x] IPFS running with a browser extension
   - [x] go-ipfs implementation
-  - [ ] js-ipfs implementation
+  - [x] js-ipfs implementation
   - [x] firefox extension
     - [x] use background go-ipfs node
     - [ ] easy install of go-ipfs node
-    - [ ] bundling of js-ipfs node
+    - [x] bundling of js-ipfs node
     - [x] url rewriting
     - [x] node management
     - [x] api configuration
@@ -758,16 +758,16 @@ We have finished step (1). We are currently working on steps (2) and (3). Step (
   - [x] chrome extension
     - [x] use background go-ipfs node
     - [ ] easy install of go-ipfs node
-    - [ ] bundling of js-ipfs node
+    - [x] bundling of js-ipfs node
     - [x] url rewriting
     - [ ] node management
     - [ ] api configuration
     - [ ] simple UX for users
-    - [ ] expose ipfs and p2p in the browser window
+    - [x] expose ipfs and p2p in the browser window
 - [ ] IPFS running natively in a browser
   - [x] go-ipfs implementation (for chrome or firefox)
     - [ ] go-ipfs static lib (for chrome or firefox)
-  - [ ] js-ipfs implementation (for chrome or firefox)
+  - [x] js-ipfs implementation (for chrome or firefox)
   - [ ] rust-ipfs implementation (for servo)
   - [ ] chromium patches adding IPFS support
   - [ ] firefox patches adding IPFS support
@@ -796,10 +796,10 @@ We have an ipfs node "management console" GUI, delivered as a distributed webapp
     - [x] adding files (+ drag and drop)
   - [x] tail logs (json)
   - [x] view & edit config (json)
-- [ ] webui console v1
+- [x] webui console v1
   - [x] webapp redesign
   - [x] peer map (flat and 3D)
-  - [ ] new dag explorer
+  - [x] new dag explorer
   - [x] new file explorer
     - [x] file navigation
     - [x] drag and drop support