From 8a0929359cca710db51fc2f4f0457fe6a0ee32fc Mon Sep 17 00:00:00 2001
From: David Dias <daviddias.p@gmail.com>
Date: Sat, 15 Sep 2018 11:21:46 -0700
Subject: [PATCH 1/4] docs: 2018 Q4 OKRs

---
 OKR.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/OKR.md b/OKR.md
index 99fae519df..0d8e9cdc51 100644
--- a/OKR.md
+++ b/OKR.md
@@ -2,6 +2,10 @@
 
 We try to 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.
 
+## 2018 Q4
+
+Writting in Progress
+
 ## 2018 Q3
 
 Find the **js-ipfs OKRs** for 2018 Q3 at the [2018 Q3 IPFS OKRs Spreadsheet](https://docs.google.com/spreadsheets/d/19vjigg4locq4fO6JXyobS2yTx-k-fSzlFM5ngZDPDbQ/edit#gid=274358435)

From 27be7dd618358ce3cf3fda0c6880e08541248933 Mon Sep 17 00:00:00 2001
From: Alan Shaw <alan.shaw@protocol.ai>
Date: Tue, 25 Sep 2018 23:26:34 +0100
Subject: [PATCH 2/4] docs: first pass Q4 OKRs

---
 OKR.md | 26 +++++++++++++++++++++++++-
 1 file changed, 25 insertions(+), 1 deletion(-)

diff --git a/OKR.md b/OKR.md
index 0d8e9cdc51..eccd702344 100644
--- a/OKR.md
+++ b/OKR.md
@@ -4,7 +4,31 @@ We try to frame our ongoing work using a process based on quarterly Objectives a
 
 ## 2018 Q4
 
-Writting in Progress
+# 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 part of the IPFS gateways
+* 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
+
+# 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 and reliability. 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 is an option for all Protocol Labs JS projects. 3 IPFS/IPLD/libp2p projects are setup to be continuously deployed
+* P1 - @achingbrain - A draft spec for unixfs-v2 is written
 
 ## 2018 Q3
 

From 159af4a5c819bab32882484db5bde0e669fd372e Mon Sep 17 00:00:00 2001
From: Alan Shaw <alan.shaw@protocol.ai>
Date: Wed, 26 Sep 2018 11:56:23 +0100
Subject: [PATCH 3/4] Update OKR.md

---
 OKR.md | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/OKR.md b/OKR.md
index eccd702344..43f4102e44 100644
--- a/OKR.md
+++ b/OKR.md
@@ -4,31 +4,32 @@ We try to frame our ongoing work using a process based on quarterly Objectives a
 
 ## 2018 Q4
 
-# A viable alternative to Go IPFS
+### 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 part of the IPFS gateways
+* 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
+### 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
+### 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 and reliability. The refactored modules are part of a JS IPFS release
+* 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 is an option for all Protocol Labs JS projects. 3 IPFS/IPLD/libp2p projects are setup to be continuously deployed
-* P1 - @achingbrain - A draft spec for unixfs-v2 is written
+* 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
 
 ## 2018 Q3
 

From c77e5295a0e8ddcca2964d55c539eb2f5bf2007f Mon Sep 17 00:00:00 2001
From: Alan Shaw <alan.shaw@protocol.ai>
Date: Fri, 28 Sep 2018 10:33:49 +0100
Subject: [PATCH 4/4] docs: add link to Q4 2018 OKRs

---
 OKR.md | 27 +--------------------------
 1 file changed, 1 insertion(+), 26 deletions(-)

diff --git a/OKR.md b/OKR.md
index 43f4102e44..f4a9546fce 100644
--- a/OKR.md
+++ b/OKR.md
@@ -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)
 
 ## 2018 Q3