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.
| IPFS Project Operations | Priority | Owner | Mid-Q Actual | Mid-Q Projection | End-Q | ** Issue Link** |
|---|---|---|---|---|---|---|
| **** | P0-P4 | 0.2 | 0.4 | 0.0 | ||
| 1 IPFS Implementations are shipping quality releases on a schedule (Alan, Steven) | ||||||
| Ship a release policy and defined quality bar, and send 1+ go-ipfs release through all stages |  |
stebalien | 🌎 | |||
| Core implementation testing gives us automated, extensive feedback on performance/reliability on a per PR and nightly basis (testing improvements) | |
stebalien | 🌎 | |||
| Improve overall state of js-ipfs tests | |
hugomrdias | 🌎 | |||
| Collaborations & other WGs aren’t blocked on core implementation release schedule for feedback/iteration/launches |  |
alanshaw | ||||
| Go and js implementations have systematized operation policies (eg issue triage, response time, etc), and a github bot to automate reminders | |
alanshaw | ||||
| We have a documented engineering design review process and send 1+ protocol improvement through the process to gain early alignment | |
stebalien | ||||
| Core implementation has improved API/CLI test coverage. | |
alanshaw | ||||
| We have documented lead maintainers for all active go and js repos |  |
stebalien | ||||
| 2 The IPFS Community is informed of relevant news in a timely manner (Molly, Dietrich) | ||||||
| We proactively update the community about important news and project progress, shipping at least one post per month | |
momack2 | 0.7 | 1 | ||
| We have a blog content plan and schedule, covering Camp content, important news, collaborations and recent event participation | |
autonome | 0.0 | 1 | ||
| We have a communications runbook for common and emergency situations | |
autonome | 0.0 | 1 | ||
| We define and start measuring a metric for tracking community support needs | |
autonome | 0 | 0.5 | ||
| 3 Collaborations are systematized and prioritized (Dietrich, Arkadiy) | ||||||
| Daily operations of collabs are supported by tooling and process that enables prioritization, metrics and manageable level of daily overhead | |
parkan / autonome | 0.5 | 1 | ||
| Opportunities are classified, prioritized and serviced in a pipeline process | |
parkan / autonome | 0.5 | 1 | ||
| IPNS over DNS production ready | |
hugomrdias | 🌎 | |||
| We have a single list of who is using IPFS and can use that information to make decisions | |
parkan / autonome | 0.5 | 1 | ||
| Opera is receiving the support they need for implementation | |
lidel / autonome | ||||
| Brave users can share and discover data with JS-IPFS embedded node | |
lidel | ||||
| ENS ships a mutable naming service using IPFS, improving the developer experience of pointing at IPFS/IPNS/IPLD content paths from smart contracts | |
lidel | ||||
| 4 Research is projecting the present into the future (David) | ||||||
| IPFS & libp2p team’s get a Workshop (through Zoom) with a Survey on the state of the art around P2P | |
yiannis | ||||
| Publish a report on the state of Research in IPFS & Libp2p | |
daviddias | ||||
| Deliver an IPFS Workshop at ACM/ICN | |
daviddias / yiannis | ||||
| 5 Lower priority projects are clearly owned and maintained (Dietrich) | ||||||
| IPFS Desktop and Web UI are tested and released with when there is a new release of go-ipfs, or in response to discovery of P0 bugs. | |
autonome / hacdias |
The Project Working Group was formed in 2018 Q4