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

OKRs - 2019 Q1 Project WG #793

Merged
merged 14 commits into from
Feb 11, 2019
Merged

OKRs - 2019 Q1 Project WG #793

Changes from 13 commits
Commits
Show all changes
14 commits
Select commit Hold shift + click to select a range
2b9b287
docs: 2019 Q1 Project WG OKRs
daviddias Dec 9, 2018
f56b980
first pass at writting the OKRs down for review
daviddias Dec 18, 2018
95cd86d
Update PROJECT.md
daviddias Dec 18, 2018
1fa039a
Update PROJECT.md
daviddias Dec 18, 2018
54026fb
Update PROJECT.md
daviddias Dec 18, 2018
6bbe55f
Update OKR/PROJECT.md
momack2 Dec 19, 2018
4c040e8
docs: add collabs KRs proposed by Molly and Arkadiy
daviddias Dec 19, 2018
8ea29e9
update OKRs based on the Timeline exercise of yesterday
daviddias Dec 19, 2018
79f579d
added myself and mikeal to areas we had expressed plans to work on
momack2 Dec 19, 2018
7c1ffba
deleted a dupe row and added prios
momack2 Dec 19, 2018
3f068bf
update ipfsconf kr
daviddias Dec 19, 2018
4d22f74
sort
daviddias Dec 19, 2018
b2d6aaf
docs: apply review based on last comments
daviddias Jan 10, 2019
c3e02f3
Update OKR/PROJECT.md
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
23 changes: 22 additions & 1 deletion OKR/PROJECT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,29 @@

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.

## 2018 Q4
## 2019 Q1
momack2 marked this conversation as resolved.
Show resolved Hide resolved

- **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
Copy link
Contributor

Choose a reason for hiding this comment

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

@parkan are you onboard with doing quarterly user reports? My understanding is this would include lots of user experience work over collab requests - so not sure if @meiqimichelle or I would make a better DRI for packaging and phrasing this from a product/UXR perspective.

Copy link
Contributor

Choose a reason for hiding this comment

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

@parkan are you onboard to own this?

- `P1` - @momack2 - Working group roadmaps are solidified, presented, and used to chart Q1 and Q2 planning
momack2 marked this conversation as resolved.
Show resolved Hide resolved
- **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

momack2 marked this conversation as resolved.
Show resolved Hide resolved
momack2 marked this conversation as resolved.
Show resolved Hide resolved
## 2018 Q4

- [Project 2018 Q4 OKRs](https://docs.google.com/spreadsheets/d/139lROP7-Ee4M4S7A_IO4iIgSgugYm7dct620LYnalII/edit#gid=1562851442)
- [Open Planning Thread](https://github.com/ipfs/project/pull/3)
Expand Down