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

OKRs - 2019 Q1 Go Core Dev #794

Merged
merged 7 commits into from
Mar 18, 2019
Merged

OKRs - 2019 Q1 Go Core Dev #794

Changes from 6 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
95f7617
2019 Q1 Go Core Dev OKRs
Dec 10, 2018
0409db9
Update GO_CORE.md
Dec 12, 2018
97e9aa1
Update GO_CORE.md
Dec 18, 2018
90c2102
Update GO_CORE.md
Dec 19, 2018
81f7724
Update GO_CORE.md
Dec 19, 2018
e39e7be
Adding Q1 endeavors from 2019 roadmap
momack2 Feb 1, 2019
bbff547
move OKRs to sheet and add link
momack2 Feb 5, 2019
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
37 changes: 37 additions & 0 deletions OKR/GO_CORE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,43 @@

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

### Data transfer is fast and efficient
* It takes less than 48 hours to transfer 1TB dataset over Fast Ethernet (100Mbps)
* Bitswap refactor + improvements reduce number of duplicate blocks downloaded by 75%
* Transfers of sparsely provided data are roughly as efficient as fully provided content
* Awesome go-ipfs benchmark test suite exists comparing ipfs performance and transfer size relative to bittorrent
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
* Awesome go-ipfs benchmark test suite exists comparing ipfs performance and transfer size relative to bittorrent
* Awesome go-ipfs benchmark test suite exists comparing ipfs performance and transfer size relative to bittorrent
* go-ipfs data transfer is thoroughly tested as part of the CI pipeline

This is in the spreadsheet right now, so adding it here for clarity

* Implement GraphSync to make accessing files in large directories log(n) faster

### Adding and providing large data sets works efficiently
* Create Provider Strategies system that is solely responsible for providing
* Implement provider strategy such that a user can add (and provide) npm or tr-wikipedia without turning off providing and without significantly impacting finding content
momack2 marked this conversation as resolved.
Show resolved Hide resolved
* Providing does not negatively impact go-ipfs's performance when fetching content.

### Datastore works efficiently for large data sets
* Complete development of benchmarks to test speed and reliability across a wide range of datastore sizes
* A new datastore implementation, suitable for very large data volumes, is adopted as default in go-ipfs

### go-ipfs becomes a well maintained project
* Every non-trivial PR is first reviewed by someone other than @Stebalien.
* A work-tracking process is adopted that allows the team to easily track the highest priority unclaimed issues, see the status of in progress work, and know which PRs need review, easily.
* Every file with a non-trivial change gets fully documented. (!)

### go-ipfs is easy to integrate with
* Extract CoreAPI interface from go-ipfs
* Implement CoreAPI HTTP API
* A new flexible and performant RPC API is designed
* base32 is supported and enabled by default
* Refactored IPFS constructor

### Optimize developer velocity
* go-ipfs developers are no longer adversly affected by gx

### Complete outstanding endeavours that are still high priorities
* New fuse mount implementation replaces the existing one
* Add mutable methods (r+w) to the new mount implementation and get it building+tested on all supported platforms

## 2018 Q4

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