Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

2018 Q4 OKRs Planning #1566

Merged
merged 4 commits into from
Sep 28, 2018
Merged
Changes from 1 commit
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
27 changes: 1 addition & 26 deletions OKR.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,32 +4,7 @@ We try to frame our ongoing work using a process based on quarterly Objectives a

## 2018 Q4

### A viable alternative to Go IPFS

* P0 - @vasco-santos - DHT is enabled by default and interoperates with Go IPFS DHT
* P1 - @vasco-santos - IPNS is functional over pubsub and the DHT
* P0 - @alanshaw - Base32 CIDv1 migration is complete
* P0 - @alanshaw - A JS IPFS daemon is one (or more!) of the IPFS gateway nodes
* P2 - @hugomrdias - JS IPFS runs on the same ports as Go IPFS and uses the same binary name
* P2 - @hugomrdias - An IPFS version manager CLI tool exists to switch between go/js/whatever versions e.g. nvm/nave
* P0 - @achingbrain - npm-on-ipfs is the default registry that IPFS developers and CI use to install npm dependencies
* P1 - @achingbrain - A repo migration tool exists and JS IPFS can automatically upgrade older repos

### Measurably faster and smaller than ever before

* P0 - @hugomrdias - JS IPFS is capable of transferring a large dataset like ImageNet at least 75% as fast as Go IPFS
* P2 - @hugomrdias - The browser bundle of IPFS is not more than 1.5MB (gzipped) in size
* P3 - @hugomrdias - Browser bundle size is measured over time and developers alerted if it increases above 1.5MB
* P1 - @alanshaw - A website is published to visually track a set of basic performance profiles of JS IPFS releases over historical versions

### Stable and future proof

* P0 - @hugomrdias - Error codes are added to all errors that originate directly from JS IPFS
* P2 - @alanshaw - Test quality is improved, duplicates removed and coverage increased
* P0 - @achingbrain - js-ipfs-unixfs-engine is decomposed into smaller modules for better maintainability, testability, reliability and reuse. The refactored modules are part of a JS IPFS release
* P2 - @achingbrain - Candidate modules for extraction from JS IPFS (e.g. js-ipfs-mfs) are identified and agreed
* P1 - @achingbrain - Continuous deployment requirements for infra are established making CD an option for all PL JS projects. 3 IPFS/IPLD/libp2p projects are setup to be continuously deployed
* P2 - @achingbrain - A draft spec for unixfs-v2 is finalized
Find the **js-ipfs OKRs** for 2018 Q4 at the [2018 Q4 IPFS OKRs Spreadsheet](https://docs.google.com/spreadsheets/d/139lROP7-Ee4M4S7A_IO4iIgSgugYm7dct620LYnalII/edit#gid=274358435)
Copy link
Member Author

Choose a reason for hiding this comment

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

⚡️👏🏽👍🏽


## 2018 Q3

Expand Down