OKRs - 2019 Q2 Project WG

## Project WG OKRs
It's time for us to work on our OKRs for Q2 2019. We should keep in mind our WG goals as expressed in our [roadmap](https://github.com/ipfs/roadmap/blob/master/WG_PROJECT.md). We'll use this PR for proposals and discussions of OKRs the next quarter. 

ref #902

- [ ] [Score 2019 Q1 OKRs](https://docs.google.com/spreadsheets/d/1BtOfd7s9oYO5iKsIorCpsm4QuQoIsoZzSz7GItE-9ys/edit?ts=5c2f3d49#gid=1681757723)
- [ ] [Async Retrospective](https://docs.google.com/document/d/1xW6aoSGOPLVbIGJe2c3FrSf5I7n7Qb79711mNa2aHjE/edit#heading=h.6tahnexchfr1)
- [ ] 2019 Q2 OKRs Open Planning (this thread)
- [ ] Move 2019 Q2 OKRs to [2019 Q1 OKRs Spreadsheet](https://docs.google.com/spreadsheets/d/1YSeyWqXh3ImanRrTkYQHHkCofiORn68bYqM_KTLBlsA/edit#gid=1681757723)

OKR/PROJECT.md

@@ -2,28 +2,15 @@
 
 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 Q2
+- In progress
+
 ## 2019 Q1
+- [Project 2019 Q1 OKRs](https://docs.google.com/spreadsheets/d/1BtOfd7s9oYO5iKsIorCpsm4QuQoIsoZzSz7GItE-9ys/edit?ts=5c2f3d49#gid=1562851442)
+- [Planning Thread](https://github.com/ipfs/team-mgmt/pull/793)
 
-- **The IPFS Org gets a fully dedicated Package Managers Working Group**
-  - `P0` - @daviddias - A Package Manager Working Group Roadmap is created
-  - `P1` - @??? - Onboard 1+ contributors to Package Managers Working Group
-- **Support and guide the IPFSConf planning and Content Curation**
-  - `P0` - @daviddias - The IPFSConf is scheduled, announced and there is a CFP running. The IPFSConf Org Team is supported by the IPFS org.
-  - `P0` - @momack2 - The IPFS Org (Working Groups & Core Contributors) has a unified plan with goals for IPFSConf
-- **The IPFS Working Groups feel supported and they have the information they need to make the best decisions**
-  - `P0` - @mikeal - We gather, process and present metrics for the IPFS Project  
-  - `P1` - @parkan - Ship the first IPFS User Quarterly Report. It documents achievements and demos of new capabilities
-  - `P1` - @momack2 - Working group roadmaps are solidified, presented, and used to chart Q1 and Q2 planning
-- **The IPFS Community is supportive, responsive, and easy to get onboarded to**
-  - `P0` - @parkan - There are zero dropped/mishandled collabs  
-  - `P1` - @parkan - Biweekly updates published to IPFS working groups highlighting patterns in top developer needs
-  - `P1` - @daviddias - The Working Groups are listed on the IPFS Website (ref: ipfs/project#14)
-  - `P2` - @parkan - Ship strategy document outlining tooling, pipeline, and management for collabs with the IPFS Project  
-  - `P2` - @parkan - 10 collab engagements result in valuable output for the wider community (feature, blog post, collaborative meeting, bug fix, etc)  
-- **The IPFS Projects have assigned maintainers, are well documented and users have good resources to rely on**
-  - `P0` - @daviddias - Reboot the IPFS Specifications repo and create a coordinated effort to write and maintain the specifications
-  - `P1` - @daviddias - Expand the Lead Maintainer Protocol to become the Maintainer Protocol for the entire organization
-- `P1` - @momack2 - IPFS gets a Public and Structured Dev Grant Program
 ## 2018 Q4
 
 - [Project 2018 Q4 OKRs](https://docs.google.com/spreadsheets/d/139lROP7-Ee4M4S7A_IO4iIgSgugYm7dct620LYnalII/edit#gid=1562851442)