Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
122 lines (104 sloc) 9.08 KB

IPFS Project Working Group - 2019 Roadmap

The IPFS Project Working Group serves as the point of coordination for the IPFS Organization.

Responsibilities include:

  • Maintain the IPFS Project Roadmap and Vision.
  • Provide coaching to Working Groups to develop their own planning and goal-setting.
  • Facilitate communication and alignment across the organization.
  • Research, develop and build new ways to help async teams coordinate at scale.
  • Recognize needs of the project and develop solutions to meet them.
  • Spin up new working groups or projects to meet IPFS project needs.

Current Projects

  • team-mgmt repo (tools and guides for the IPFS Team to coordinate with itself and the community)
  • IPFS Roadmap & supporting tools and materials
  • depviz - https://github.com/ipfs/pm/issues/132 (adopted)
  • 2018 Team Structure and 2019 projections

🚀 Major 2019 goals to achieve

The major goals below and following milestones have been labeled with the emoji for the goal in the IPFS Project Roadmap that they contribute towards: 📦 = Package Managers 🤝 = Partner Use Cases

(Note: we also have many 🧠 = Strategic Projects)

  • 1) The IPFS org has clearly communicated vision, goals, and priorities to align and accelerate project development and adoption. 📦 🤝 🧠
  • 2) A baseline suite of Coordination Strategies and Tools becomes first nature to the org. These have minimal overhead without losing clarity and productivity. 📦 🤝 🧠
  • 3) The IPFS org increases its ability to operate at scale (ability to support a growth of 1 order of magnitude in the number of contributors, from X,000 to X0,000). 📦 🤝 🧠

💎 Milestones

Audit and improve our team guides, tools, and processes

  • M (P1): The InterPlanetary Community Handbook is Published 🧠
    • A gitbook (or similar) containing the project values, how we organize ourselves, code of conduct, contributing guidelines and so on.
    • A new contributor spends less than a week onboarding into the community.
    • Roles & Responsibilities for team members and captains are well defined
    • It describes the Protocol Governance and how decisions are made.
  • M (P1): Quarterly IPFS User Reports from our direct partners/collaborators and broad Users, exist and are useful to the Working Groups 🤝
    • Quarterly Reports are published that Highlight top user needs, feature requests, and pain points
  • M (P2): Roadmap is updated and published with 2020+ plans 🧠
  • M (P2): The IPFS org makes decisions based on user research 🤝 🧠
    • Working Groups have user researcher support to coordinate User Research efforts across the IPFS Project. Everyone can benefit from the output.
    • We have 6+ user researchers as full time contributors on IPFS projects
  • M (P3): Evaluate the current set of tools/services we use to run our org and compare it with potential alternatives 🧠
    • List all the current ones we use
    • Explore and evaluate others (i.e. Gitlab)
    • Contribute to the analysis of the impact of OKRs in the IPFS Org

Grow, support, and bootstrap IPFS working groups

  • M (P0): Bootstrap a Package Managers Working group 📦 🧠
    • The IPFS Organization dogfoods Package Managers with IPFS
    • The WG adopts GX and npm-on-ipfs as their products
    • Gx is fast, efficient, and saves go developers time with 1+ fulltime maintainer
    • Create the Package Managers Working Group Roadmap in advance (even before the WG exists) containing all the insights from the 2019 Roadmapping endeavour
  • M (P0): IPFS Events are open and planned proactively 🧠
    • IPFS Dev Meetings happen again
    • IPFSConf increases IPFS usage, # of applications on IPFS, community growth, and external awareness/engagement
    • Hack Weeks, Research Weeks and WG Gatherings are planned
  • M (P0): Grow the Project WG with folks at full time capacity 🧠
    • We have at least the equivalent of 4 people full time
    • Project WG has an easy way to track cross-wg issues, blockers, and endeavors
  • M (P0): IPFS Documentation & Specifications are organized, updated, and have 4+ active maintainers 🧠
  • M (P0): IPFS gets a solid Security Program 📦 🤝 🧠
    • We have 2+ fulltime contributors to lead Security for IPFS
    • IPFS has a Responsible Disclosure Program
    • IPFS gets regularly audited
  • M (P2): Bootstrap Offline/Mobile working groups to prepare for 2020 work towards distributed web vision 🧠

Continue supporting a growing IPFS community while keep everyone excited and involved 🧠

  • M (P1): The community receives Quarterly IPFS Project Reports (similar to the Filecoin updates) 🤝
    • Highlight achievements by each Working Group
    • Contain demos of what has been released
  • M (P1): Create Large Research Contests for IPFS internals, driving adoption through enthusiasm and practice 🧠 📦
    • Block Exchange (Improve on Bitswap)
    • Graph Exchange (Improve on GraphSync)
  • M (P1): IPFS gets a Public and Structured Dev Grant Program 🧠 📦
    • At least 50 projects are published under this grant program
  • M (P3): IPFS collaborates with PL Research and creates a Public Research Grant Program dedicated to IPFS Open Problems 🧠 📦
    • At least 50 Open Problems are published
    • 100% of the proposals are evaluated

Timeline

  • Q1
    • M (P0): Bootstrap a Package Managers Working group 📦 🧠 (Part 1: Roadmap, Onboard Owners for npm on IPFS, GX and partner relationships)
    • M (P1): IPFS gets a Public and Structured Dev Grant Program 🧠 📦 (Part 1: Launch program)
    • M (P1): The community receives Quarterly IPFS Project Reports (similar to the Filecoin updates) 🤝 (Part 1: Q1 Report)
    • M (P1): Quarterly IPFS User Reports from our direct partners/collaborators and broad Users, exist and are useful to the Working Groups 🤝 (Part 1: Q1 Report)
    • M (P0): IPFS Events are open and planned proactively 🧠
    • M (P0): IPFS Documentation & Specifications are organized, updated, and have 4+ active maintainers 🧠
    • M (P2): The IPFS org makes decisions based on user research 🤝 🧠 (Part 1: onboard some UXR support)
  • Q2
    • M (P0): Grow the Project WG with folks at full time capacity 🧠
    • M (P0): Bootstrap a Package Managers Working group 📦 🧠 (Part 2: Understand Package Manager Ecosystem Needs. Ensure that those are covered by the Core Impl work.)
    • M (P1): The community receives Quarterly IPFS Project Reports (similar to the Filecoin updates) 🤝 (Part 2: Q2 Report)
    • M (P1): The InterPlanetary Community Handbook is Published 🧠 (Part 1: Drafted)
    • M (P1): Quarterly IPFS User Reports from our direct partners/collaborators and broad Users, exist and are useful to the Working Groups 🤝 (Part 2: Q2 Report)
    • M (P0): IPFS gets a solid Security Program 📦 🤝 🧠 (Depends on LabOS figuring out the Security Team for PL)
    • M (P2): The IPFS org makes decisions based on user research 🤝 🧠 (Part 2: integrate into decision making)
    • M (P1): Create Large Research Contests for IPFS internals, driving adoption through enthusiasm and practice 🧠 📦 Part 0: preliminary planning)
  • Q3
    • M (P0): Bootstrap a Package Managers Working group 📦 🧠 (Part 3: The world (the Package Managers we work with first) starts defaulting to IPFS as a transport.)
    • M (P1): Quarterly IPFS User Reports from our direct partners/collaborators and broad Users, exist and are useful to the Working Groups 🤝 (Part 3: Q3 Report)
    • M (P1): The community receives Quarterly IPFS Project Reports (similar to the Filecoin updates) 🤝 (Part 3: Q3 Report)
    • M (P1): Create Large Research Contests for IPFS internals, driving adoption through enthusiasm and practice 🧠 📦 (part 1: Block Exchange grant)
    • M (P1): The InterPlanetary Community Handbook is Published 🧠 (Part 2: LAUNCH - ?@ipfs conf?)
    • M (P1): IPFS gets a Public and Structured Dev Grant Program 🧠 📦 (Part 2: target number of grants issued)
    • M (P2): Bootstrap Offline/Mobile working groups to prepare for 2020 work towards distributed web vision 🧠
    • M (P3): Evaluate the current set of tools/services we use to run our org and compare it with potential alternatives 🧠
  • Q4
    • M (P1): Create Large Research Contests for IPFS internals, driving adoption through enthusiasm and practice 🧠 📦 (Part 2: Graph Exchange grant)
    • M (P1): Quarterly IPFS User Reports from our direct partners/collaborators and broad Users, exist and are useful to the Working Groups 🤝 (Part 4: Q4 Report)
    • M (P1): The community receives Quarterly IPFS Project Reports (similar to the Filecoin updates) 🤝 (Part 4: Q4 Report)
    • M (P2): Roadmap is updated and published with 2020+ plans 🧠
    • M (P3): IPFS collaborates with PL Research and creates a Public Research Grant Program dedicated to IPFS Open Problems

⁉️ Want to get involved?

You can’t perform that action at this time.