OKRs - 2019 Q2 Project WG

[momack2]

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. We'll use this PR for proposals and discussions of OKRs the next quarter.

ref #902

• Score 2019 Q1 OKRs
• Async Retrospective
• 2019 Q2 OKRs Open Planning (this thread)
• Move 2019 Q2 OKRs to 2019 Q1 OKRs Spreadsheet

[momack2]

Some tentative OKRs:

The Org levels-up around

• Coordinate first Security Audit (and init responsible disclosure program??)
• Working Groups outline, plan and start collecting metrics that measure the success of their objectives
• KPIs are used as tools to make good decisions by working groups

IPFS Contributors are aligned, empowered, and motivated

• IPFS Team week is rated as "extremely useful" (on avg 4.5/5) by attendees
• 100% of IPFS team week contributors take trainings on X, Y, and Z (async/distributed communication training, sexual harassment training, (self)management training, ??)

IPFS Camp increases project community and engagement

• IPFS Camp attendees rate the event on avg 4.5/5 in terms of time well spent and increased engagement with the project
• IPFS Camp creates XX new public education materials which get over YY engagements from the wider community
• IPFS Camp spawns XX new or deepened collabs that increase total IPFS value created

IPFS external communication and collaboration become more strategic and systematized

• Ship the first IPFS User Quarterly Report documenting achievements and demos of new capabilities
• Our collaborations pipeline is systematized and collects key metrics to empower prioritization
• Optimize collaborations pipeline to better engage with key community members and surface needs to the team
• Biweekly updates published to IPFS working groups highlighting patterns in top developer needs
• Community / Comms / Docs is a staffed and focused area of investment for the IPFS org

Here's our Q2 Roadmap for reference: https://github.com/ipfs/roadmap/blob/master/WG_PROJECT.md#-timeline

[terichadbourne]

I’d love to hear more about this one: “100% of IPFS contributors take trainings on X, Y, and Z (async/distributed communication training, sexual harassment training, (self)management training”

At first glance, it seems to me to be very appropriate for contributors who happen to be employed to work on IPFS, but like overreach and. barrier to entry for others.

To be clear, I totally support a Code of Conduct, and providing these resources optionally to all contributors is a cool idea, but an expectation of 100% sounds like a mandate.

I’m envisioning the experience of someone who’s exploring IPFS and comes across docs that need a quick fix. If, as part of opening a PR to submit that fix, they found themselves required to take 1-3 hours of training, I suspect they’d never follow their instincts to make that contribution.

What kind of setup do you have in mind for these offerings?

[momack2]

Thanks for the note @terichadbourne! I was thinking specifically around the IPFS/PL Team Week as a venue for running such trainings for IPFS/PL contributors. Good point that I both wasn't clear and this may not be the right venue to track that work...