JS_CORE.md

JS Core OKRs

We frame our ongoing work using a process based on quarterly Objectives and Key Results (OKRs). Objectives reflect outcomes that are challenging, but realistic. Results are tangible and measurable.

2019 Q1

A complete implementation of IPFS in JavaScript

• p0 - Base32 encoded version 1 CIDs are the default for new content added to IPFS @alanshaw
• p0 - IPNS has a streaming API @vasco-santos
• p1 - IPNS supports ttl, dhtt and dhtrc parameters and republish configurations @vasco-santos
• p1 - A repo migration tool exists and JS IPFS can automatically upgrade older repos @achingbrain

Used in production

• p0 - A JS IPFS daemon is one (or more!) of the IPFS gateway nodes @alanshaw
• p2 - Perf benchmarking site is launched and 10 different benchmarking scenarios exist @alanshaw

Inviting for developers and contributors

• p1 - Continuous deployment drives js-ipfs-unixfs-* and js-ipfs-mfs @achingbrain
• p1 - Core APIs are refactored to use async await/iterators; at least half the repos in scope have a proposal/PR @alanshaw

Underpins the most popular package managers

• p0 - IPFS is a transport for npm/tink @achingbrain
• p2 - Homebrew is available on IPFS @achingbrain

2018 Q4

• js-ipfs 2018 Q4 OKRs
• Open Planning Thread
• Previous Quarter Retrospective

2018 Q3

• js-ipfs 2018 Q3 OKRs
• Open Planning Thread
• Previous Quarter Retrospective

2018 Q2

• js-ipfs 2018 Q2 OKRs
• Open Planning Thread

2018 Q1

• js-ipfs 2018 Q1 OKRs