From 2b9b2877d2581b8ceef54ea424d808ee9c8949ac Mon Sep 17 00:00:00 2001 From: David Dias Date: Sun, 9 Dec 2018 12:21:17 +0100 Subject: [PATCH 01/14] docs: 2019 Q1 Project WG OKRs --- OKR/PROJECT.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/OKR/PROJECT.md b/OKR/PROJECT.md index 142f74d4..4468ab5c 100644 --- a/OKR/PROJECT.md +++ b/OKR/PROJECT.md @@ -2,8 +2,11 @@ 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 + +`Writting in Progress` +## 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) From f56b980745a7e14ce3da1d19e5e934284e47c4de Mon Sep 17 00:00:00 2001 From: David Dias Date: Tue, 18 Dec 2018 11:35:19 +0000 Subject: [PATCH 02/14] first pass at writting the OKRs down for review --- OKR/PROJECT.md | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-) diff --git a/OKR/PROJECT.md b/OKR/PROJECT.md index 4468ab5c..d6e5e921 100644 --- a/OKR/PROJECT.md +++ b/OKR/PROJECT.md @@ -4,8 +4,24 @@ We frame our ongoing work using a process based on quarterly Objectives and Key ## 2019 Q1 -`Writting in Progress` - +- **The IPFS Org gets a fully dedicated Package Managers Working Group** + - `PX` - @??? - A Package Manager Working Group Roadmap is created + - `PX` - @??? - Onboard 2+ contributors to this Working Group +- **Support and guide the IPFSConf planning and Content Curation** + - `PX` - @daviddias - The IPFSConf is scheduled, announced and there is a CFP published + - `PX` - @??? - Working Groups have their goals established for IPFSConf +- **The IPFS Working Groups feel supported and they have the information they need to make the best decisions ** + - `PX` - @??? - Ship the first IPFS User Quarterly Report. It documents achievements and demos of new capabilities + - `PX` - @??? - We gather, process and present metrics for the IPFS Project + - `PX` - @??? - We grow the Project WG to have a team capable of answering to all IPFS Working Group needs. + - `PX` - @??? - Working group roadmaps are solidified, presented, and used to chart Q1 and Q2 planning +- **The Working Groups are widely known in the IPFS Community and easy to get onboarded to** + - `PX` - @??? - The Working Groups are listed on the IPFS Website (ref: ipfs/project#14) + - `PX` - @??? - We successfully improve the onboarding experience which translates to seeing 3+ new contributors engaged per Working Group until the end of the Quarter +- **The IPFS Projects have assigned maintainers, are well documented and users have good resources to rely on** + - `PX` - @??? - Expand the Lead Maintainer Protocol to become the Maintainer Protocol for the entire organization + - `PX` - @??? - Reboot the IPFS Specifications repo and create a coordinated effort to write and maintain the specifications + ## 2018 Q4 - [Project 2018 Q4 OKRs](https://docs.google.com/spreadsheets/d/139lROP7-Ee4M4S7A_IO4iIgSgugYm7dct620LYnalII/edit#gid=1562851442) From 95cd86dbbf967320e95257f9b9da1cd51ce36595 Mon Sep 17 00:00:00 2001 From: David Dias Date: Tue, 18 Dec 2018 11:35:39 +0000 Subject: [PATCH 03/14] Update PROJECT.md --- OKR/PROJECT.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/OKR/PROJECT.md b/OKR/PROJECT.md index d6e5e921..c2755445 100644 --- a/OKR/PROJECT.md +++ b/OKR/PROJECT.md @@ -10,7 +10,7 @@ We frame our ongoing work using a process based on quarterly Objectives and Key - **Support and guide the IPFSConf planning and Content Curation** - `PX` - @daviddias - The IPFSConf is scheduled, announced and there is a CFP published - `PX` - @??? - Working Groups have their goals established for IPFSConf -- **The IPFS Working Groups feel supported and they have the information they need to make the best decisions ** +- **The IPFS Working Groups feel supported and they have the information they need to make the best decisions** - `PX` - @??? - Ship the first IPFS User Quarterly Report. It documents achievements and demos of new capabilities - `PX` - @??? - We gather, process and present metrics for the IPFS Project - `PX` - @??? - We grow the Project WG to have a team capable of answering to all IPFS Working Group needs. From 1fa039a77ce9cd73bbd80c75e1f40521bf19938f Mon Sep 17 00:00:00 2001 From: David Dias Date: Tue, 18 Dec 2018 11:38:58 +0000 Subject: [PATCH 04/14] Update PROJECT.md --- OKR/PROJECT.md | 1 + 1 file changed, 1 insertion(+) diff --git a/OKR/PROJECT.md b/OKR/PROJECT.md index c2755445..59793752 100644 --- a/OKR/PROJECT.md +++ b/OKR/PROJECT.md @@ -21,6 +21,7 @@ We frame our ongoing work using a process based on quarterly Objectives and Key - **The IPFS Projects have assigned maintainers, are well documented and users have good resources to rely on** - `PX` - @??? - Expand the Lead Maintainer Protocol to become the Maintainer Protocol for the entire organization - `PX` - @??? - Reboot the IPFS Specifications repo and create a coordinated effort to write and maintain the specifications + - `PX` - @??? - Convert our Contributing Guidelines and Team Management Tools and Practices into the InterPlanetary Community Handbook ## 2018 Q4 From 54026fbf774aec7cfc48e3ecb553adac0337e52c Mon Sep 17 00:00:00 2001 From: David Dias Date: Tue, 18 Dec 2018 12:02:19 +0000 Subject: [PATCH 05/14] Update PROJECT.md --- OKR/PROJECT.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/OKR/PROJECT.md b/OKR/PROJECT.md index 59793752..ce79047f 100644 --- a/OKR/PROJECT.md +++ b/OKR/PROJECT.md @@ -17,11 +17,11 @@ We frame our ongoing work using a process based on quarterly Objectives and Key - `PX` - @??? - Working group roadmaps are solidified, presented, and used to chart Q1 and Q2 planning - **The Working Groups are widely known in the IPFS Community and easy to get onboarded to** - `PX` - @??? - The Working Groups are listed on the IPFS Website (ref: ipfs/project#14) - - `PX` - @??? - We successfully improve the onboarding experience which translates to seeing 3+ new contributors engaged per Working Group until the end of the Quarter + - `PX` - @??? - Improve the onboarding experience successfully, which translates to seeing 3+ new contributors engaged per Working Group until the end of the Quarter - **The IPFS Projects have assigned maintainers, are well documented and users have good resources to rely on** - `PX` - @??? - Expand the Lead Maintainer Protocol to become the Maintainer Protocol for the entire organization - `PX` - @??? - Reboot the IPFS Specifications repo and create a coordinated effort to write and maintain the specifications - - `PX` - @??? - Convert our Contributing Guidelines and Team Management Tools and Practices into the InterPlanetary Community Handbook + - `PX` - @??? - Convert our Contributing Guidelines and Team Management Tools and Practices into the first edition of the InterPlanetary Community Handbook ## 2018 Q4 From 6bbe55f2005b52231f02af70a0250f0c4834b6a3 Mon Sep 17 00:00:00 2001 From: MollyM Date: Wed, 19 Dec 2018 08:13:18 +0000 Subject: [PATCH 06/14] Update OKR/PROJECT.md Co-Authored-By: daviddias --- OKR/PROJECT.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/OKR/PROJECT.md b/OKR/PROJECT.md index ce79047f..2e9755c2 100644 --- a/OKR/PROJECT.md +++ b/OKR/PROJECT.md @@ -15,7 +15,7 @@ We frame our ongoing work using a process based on quarterly Objectives and Key - `PX` - @??? - We gather, process and present metrics for the IPFS Project - `PX` - @??? - We grow the Project WG to have a team capable of answering to all IPFS Working Group needs. - `PX` - @??? - Working group roadmaps are solidified, presented, and used to chart Q1 and Q2 planning -- **The Working Groups are widely known in the IPFS Community and easy to get onboarded to** +- **The IPFS Community is supportive, responsive, and easy to get onboarded to** - `PX` - @??? - The Working Groups are listed on the IPFS Website (ref: ipfs/project#14) - `PX` - @??? - Improve the onboarding experience successfully, which translates to seeing 3+ new contributors engaged per Working Group until the end of the Quarter - **The IPFS Projects have assigned maintainers, are well documented and users have good resources to rely on** From 4c040e8d3c31a35083bba4170c96317ccf5f8e05 Mon Sep 17 00:00:00 2001 From: David Dias Date: Wed, 19 Dec 2018 08:16:43 +0000 Subject: [PATCH 07/14] docs: add collabs KRs proposed by Molly and Arkadiy --- OKR/PROJECT.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/OKR/PROJECT.md b/OKR/PROJECT.md index 2e9755c2..b3620861 100644 --- a/OKR/PROJECT.md +++ b/OKR/PROJECT.md @@ -5,19 +5,23 @@ We frame our ongoing work using a process based on quarterly Objectives and Key ## 2019 Q1 - **The IPFS Org gets a fully dedicated Package Managers Working Group** - - `PX` - @??? - A Package Manager Working Group Roadmap is created + - `P0` - @daviddias - A Package Manager Working Group Roadmap is created - `PX` - @??? - Onboard 2+ contributors to this Working Group - **Support and guide the IPFSConf planning and Content Curation** - `PX` - @daviddias - The IPFSConf is scheduled, announced and there is a CFP published - `PX` - @??? - Working Groups have their goals established for IPFSConf - **The IPFS Working Groups feel supported and they have the information they need to make the best decisions** - - `PX` - @??? - Ship the first IPFS User Quarterly Report. It documents achievements and demos of new capabilities + - `P1` - @parkan - Ship the first IPFS User Quarterly Report. It documents achievements and demos of new capabilities - `PX` - @??? - We gather, process and present metrics for the IPFS Project - `PX` - @??? - We grow the Project WG to have a team capable of answering to all IPFS Working Group needs. - `PX` - @??? - 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** - - `PX` - @??? - The Working Groups are listed on the IPFS Website (ref: ipfs/project#14) - - `PX` - @??? - Improve the onboarding experience successfully, which translates to seeing 3+ new contributors engaged per Working Group until the end of the Quarter + - `P1` - @daviddias - The Working Groups are listed on the IPFS Website (ref: ipfs/project#14) + - `PX` - @??? - Improve the onboarding experience successfully, which translates to seeing 3+ new contributors engaged per Working Group until the end of the Quarter + - `P1` - @parkan - Biweekly updates published to IPFS working groups highlighting patterns in top developer needs + - `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) + - `P0` - @parkan - There are zero dropped/mishandled collabs - **The IPFS Projects have assigned maintainers, are well documented and users have good resources to rely on** - `PX` - @??? - Expand the Lead Maintainer Protocol to become the Maintainer Protocol for the entire organization - `PX` - @??? - Reboot the IPFS Specifications repo and create a coordinated effort to write and maintain the specifications From 8ea29e9dcf6cc52df45832684090d8f9c4d7b970 Mon Sep 17 00:00:00 2001 From: David Dias Date: Wed, 19 Dec 2018 08:25:43 +0000 Subject: [PATCH 08/14] update OKRs based on the Timeline exercise of yesterday --- OKR/PROJECT.md | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) diff --git a/OKR/PROJECT.md b/OKR/PROJECT.md index b3620861..c93a0d66 100644 --- a/OKR/PROJECT.md +++ b/OKR/PROJECT.md @@ -8,24 +8,23 @@ We frame our ongoing work using a process based on quarterly Objectives and Key - `P0` - @daviddias - A Package Manager Working Group Roadmap is created - `PX` - @??? - Onboard 2+ contributors to this Working Group - **Support and guide the IPFSConf planning and Content Curation** - - `PX` - @daviddias - The IPFSConf is scheduled, announced and there is a CFP published - - `PX` - @??? - Working Groups have their goals established for IPFSConf + - `P0` - @daviddias - The IPFSConf is scheduled, announced and there is a CFP published. + - `PX` - @??? - Working Groups have their goals established for IPFSConf + - `PX` - @??? - 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** - `P1` - @parkan - Ship the first IPFS User Quarterly Report. It documents achievements and demos of new capabilities - - `PX` - @??? - We gather, process and present metrics for the IPFS Project - - `PX` - @??? - We grow the Project WG to have a team capable of answering to all IPFS Working Group needs. - - `PX` - @??? - Working group roadmaps are solidified, presented, and used to chart Q1 and Q2 planning + - `P0` - @??? - We gather, process and present metrics for the IPFS Project + - `P1` - @??? - 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** - `P1` - @daviddias - The Working Groups are listed on the IPFS Website (ref: ipfs/project#14) - - `PX` - @??? - Improve the onboarding experience successfully, which translates to seeing 3+ new contributors engaged per Working Group until the end of the Quarter + - `P1` - @??? - Improve the onboarding experience successfully, which translates to seeing 3+ new contributors engaged per Working Group until the end of the Quarter - `P1` - @parkan - Biweekly updates published to IPFS working groups highlighting patterns in top developer needs - `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) - `P0` - @parkan - There are zero dropped/mishandled collabs - **The IPFS Projects have assigned maintainers, are well documented and users have good resources to rely on** - - `PX` - @??? - Expand the Lead Maintainer Protocol to become the Maintainer Protocol for the entire organization - - `PX` - @??? - Reboot the IPFS Specifications repo and create a coordinated effort to write and maintain the specifications - - `PX` - @??? - Convert our Contributing Guidelines and Team Management Tools and Practices into the first edition of the InterPlanetary Community Handbook + - `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 ## 2018 Q4 From 79f579daeecf618aeaa0f38e9c68fc50602b421d Mon Sep 17 00:00:00 2001 From: MollyM Date: Wed, 19 Dec 2018 01:15:22 -0800 Subject: [PATCH 09/14] added myself and mikeal to areas we had expressed plans to work on --- OKR/PROJECT.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/OKR/PROJECT.md b/OKR/PROJECT.md index c93a0d66..25c255fd 100644 --- a/OKR/PROJECT.md +++ b/OKR/PROJECT.md @@ -9,15 +9,15 @@ We frame our ongoing work using a process based on quarterly Objectives and Key - `PX` - @??? - Onboard 2+ contributors to this Working Group - **Support and guide the IPFSConf planning and Content Curation** - `P0` - @daviddias - The IPFSConf is scheduled, announced and there is a CFP published. - - `PX` - @??? - Working Groups have their goals established for IPFSConf - - `PX` - @??? - The IPFS Org (Working Groups & Core Contributors) has a unified plan with goals for IPFSConf + - `PX` - @momack2 - Working Groups have their goals established for IPFSConf + - `PX` - @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** - `P1` - @parkan - Ship the first IPFS User Quarterly Report. It documents achievements and demos of new capabilities - - `P0` - @??? - We gather, process and present metrics for the IPFS Project - - `P1` - @??? - Working group roadmaps are solidified, presented, and used to chart Q1 and Q2 planning + - `P0` - @mikeal - We gather, process and present metrics for the IPFS Project + - `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** - `P1` - @daviddias - The Working Groups are listed on the IPFS Website (ref: ipfs/project#14) - - `P1` - @??? - Improve the onboarding experience successfully, which translates to seeing 3+ new contributors engaged per Working Group until the end of the Quarter + - `P1` - @mikeal - Improve the onboarding experience successfully, which translates to seeing 3+ new contributors engaged per Working Group until the end of the Quarter - `P1` - @parkan - Biweekly updates published to IPFS working groups highlighting patterns in top developer needs - `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) From 7c1ffbacbe19a18741466bc5ef65e643c5c11262 Mon Sep 17 00:00:00 2001 From: MollyM Date: Wed, 19 Dec 2018 01:17:09 -0800 Subject: [PATCH 10/14] deleted a dupe row and added prios I think we have too many P0s --- OKR/PROJECT.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/OKR/PROJECT.md b/OKR/PROJECT.md index 25c255fd..89ff66e6 100644 --- a/OKR/PROJECT.md +++ b/OKR/PROJECT.md @@ -6,11 +6,10 @@ We frame our ongoing work using a process based on quarterly Objectives and Key - **The IPFS Org gets a fully dedicated Package Managers Working Group** - `P0` - @daviddias - A Package Manager Working Group Roadmap is created - - `PX` - @??? - Onboard 2+ contributors to this Working Group + - `P0` - @??? - Onboard 2+ contributors to this Working Group - **Support and guide the IPFSConf planning and Content Curation** - `P0` - @daviddias - The IPFSConf is scheduled, announced and there is a CFP published. - - `PX` - @momack2 - Working Groups have their goals established for IPFSConf - - `PX` - @momack2 - The IPFS Org (Working Groups & Core Contributors) has a unified plan with goals for IPFSConf + - `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** - `P1` - @parkan - Ship the first IPFS User Quarterly Report. It documents achievements and demos of new capabilities - `P0` - @mikeal - We gather, process and present metrics for the IPFS Project From 3f068bf2d1113d827cdfad4a3eeeceb965511af8 Mon Sep 17 00:00:00 2001 From: David Dias Date: Wed, 19 Dec 2018 14:39:13 +0000 Subject: [PATCH 11/14] update ipfsconf kr --- OKR/PROJECT.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/OKR/PROJECT.md b/OKR/PROJECT.md index 89ff66e6..696f2d2d 100644 --- a/OKR/PROJECT.md +++ b/OKR/PROJECT.md @@ -8,7 +8,7 @@ We frame our ongoing work using a process based on quarterly Objectives and Key - `P0` - @daviddias - A Package Manager Working Group Roadmap is created - `P0` - @??? - Onboard 2+ contributors to this Working Group - **Support and guide the IPFSConf planning and Content Curation** - - `P0` - @daviddias - The IPFSConf is scheduled, announced and there is a CFP published. + - `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** - `P1` - @parkan - Ship the first IPFS User Quarterly Report. It documents achievements and demos of new capabilities From 4d22f74b12254ec23cc8e0bc6ce47d81000f1687 Mon Sep 17 00:00:00 2001 From: David Dias Date: Wed, 19 Dec 2018 15:10:16 +0000 Subject: [PATCH 12/14] sort --- OKR/PROJECT.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/OKR/PROJECT.md b/OKR/PROJECT.md index 696f2d2d..7b242fd6 100644 --- a/OKR/PROJECT.md +++ b/OKR/PROJECT.md @@ -6,21 +6,21 @@ We frame our ongoing work using a process based on quarterly Objectives and Key - **The IPFS Org gets a fully dedicated Package Managers Working Group** - `P0` - @daviddias - A Package Manager Working Group Roadmap is created - - `P0` - @??? - Onboard 2+ contributors to this Working Group + - `P1` - @??? - Onboard 2+ contributors to this 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 - - `P0` - @mikeal - We gather, process and present metrics for the IPFS Project - `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** - - `P1` - @daviddias - The Working Groups are listed on the IPFS Website (ref: ipfs/project#14) - - `P1` - @mikeal - Improve the onboarding experience successfully, which translates to seeing 3+ new contributors engaged per Working Group until the end of the Quarter + - `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) + - `P1` - @mikeal - Improve the onboarding experience successfully, which translates to seeing 3+ new contributors engaged per Working Group until the end of the Quarter - `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) - - `P0` - @parkan - There are zero dropped/mishandled collabs - **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 From b2d6aaf4f5ba3c489eb680d514823f4b43b10ce0 Mon Sep 17 00:00:00 2001 From: David Dias Date: Thu, 10 Jan 2019 08:19:45 +0100 Subject: [PATCH 13/14] docs: apply review based on last comments --- OKR/PROJECT.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/OKR/PROJECT.md b/OKR/PROJECT.md index 7b242fd6..9206b2a3 100644 --- a/OKR/PROJECT.md +++ b/OKR/PROJECT.md @@ -6,7 +6,7 @@ We frame our ongoing work using a process based on quarterly Objectives and Key - **The IPFS Org gets a fully dedicated Package Managers Working Group** - `P0` - @daviddias - A Package Manager Working Group Roadmap is created - - `P1` - @??? - Onboard 2+ contributors to this Working Group + - `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 @@ -18,7 +18,6 @@ We frame our ongoing work using a process based on quarterly Objectives and Key - `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) - - `P1` - @mikeal - Improve the onboarding experience successfully, which translates to seeing 3+ new contributors engaged per Working Group until the end of the Quarter - `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** From c3e02f3afa48f9a86d0ce9118ceee7e65a6f361c Mon Sep 17 00:00:00 2001 From: MollyM Date: Tue, 5 Feb 2019 15:01:24 -0800 Subject: [PATCH 14/14] Update OKR/PROJECT.md add dev grant program --- OKR/PROJECT.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/OKR/PROJECT.md b/OKR/PROJECT.md index 9206b2a3..48d57344 100644 --- a/OKR/PROJECT.md +++ b/OKR/PROJECT.md @@ -23,7 +23,7 @@ We frame our ongoing work using a process based on quarterly Objectives and Key - **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)