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

OKRs - 2019 Q1 JS Core WG #799

Merged
merged 6 commits into from
Feb 5, 2019
Merged

OKRs - 2019 Q1 JS Core WG #799

Changes from 2 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
d3c5bea
docs: 2019 Q1 JS IPFS WG OKRs
Dec 11, 2018
e8837ae
feat: WIP intitial stab at OKRs and prioritising
Dec 18, 2018
7dbda1d
docs: updated OKRs
Dec 19, 2018
7bdd947
Update JS_CORE.md
Dec 19, 2018
6ce59fd
refactor: drop homebrew for more complete API
Dec 19, 2018
181fa6a
feat: add connectivity KR
Dec 19, 2018
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
25 changes: 25 additions & 0 deletions OKR/JS_CORE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,31 @@

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

### TODO NAME ~implementation

* 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 publishing parameters `ttl`, `dhtt` and `dhtrc` @vasco-santos
Copy link
Member

Choose a reason for hiding this comment

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

As the dht parameters are for resolve, I would put it in the following way:

Suggested change
* p1 - IPNS supports publishing parameters `ttl`, `dhtt` and `dhtrc` @vasco-santos
* p1 - IPNS supports `ttl`, `dhtt` and `dhtrc` parameters @vasco-santos

* p1 - IPNS supports republish configurations @vasco-santos
* p1 - A repo migration tool exists and JS IPFS can automatically upgrade older repos @achingbrain

### TODO NAME ~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

Copy link
Member

Choose a reason for hiding this comment

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

Suggestion: This objective should contain a KR on "js-ipfs can find (Peer Routing) any peer and dial to it (direct or relay) if this Peer is online."

Potentially adding a job that keeps trying to dial to many different nodes in the network, just to be sure that the connection always happens.

Copy link
Member Author

Choose a reason for hiding this comment

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

Potentially adding a job that keeps trying to dial to many different nodes in the network, just to be sure that the connection always happens.

This is to mitigate against a failed connection due to network error or your laptop goes offline or something? I'm surprised this isn't already implemented!

Copy link
Member

Choose a reason for hiding this comment

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

@alanshaw I meant a job in our infra that keeps checking that JS can make quality connections everywhere as the network grows. But yeah, your proposal (if not done yet) is sound too.

### TODO NAME ~process/interface

* p1 - Continuous deployment drives `js-ipfs-unixfs-*` and `js-ipfs-mfs` @achingbrain
* p1 - JS IPFS core APIs are refactored to use async iterators and half the repos in scope have a proposal/PR @alanshaw

### JS IPFS underpins the biggest package managers

* p0 - IPFS is a transport for [npm/tink](https://github.com/npm/tink) @achingbrain
* p2 - [Homebrew](https://brew.sh/) is available on IPFS @achingbrain

## 2018 Q4

- [js-ipfs 2018 Q4 OKRs](https://docs.google.com/spreadsheets/d/139lROP7-Ee4M4S7A_IO4iIgSgugYm7dct620LYnalII/edit#gid=274358435)
Expand Down