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

OKRs - 2019 Q2 Project WG #914

Merged
merged 2 commits into from
May 10, 2019
Merged
Changes from all commits
Commits
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
29 changes: 9 additions & 20 deletions OKR/PROJECT.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,28 +2,17 @@

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
- [Project 2019 Q2 OKRs](https://docs.google.com/spreadsheets/d/1YSeyWqXh3ImanRrTkYQHHkCofiORn68bYqM_KTLBlsA/edit#gid=1562851442)
- [OKR Explanation Video](https://www.youtube.com/watch?v=VGDVjNm8ez0&list=PLuhRWgmPaHtRUYCD_RyUw2ldU4lyoSXR1&index=5)
- [Planning Thread](https://github.com/ipfs/team-mgmt/pull/914)

## 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)
Expand Down