Milestones

• short-term - current status
• medium-term - dev under team guidance/stewardship
• long-term - transition to public

Features

• multi-player mode
• facilitates development of commons in platform itself
  • stakeholders
  • dev/research team
  • participants
    • maintainers
    • contributors
  • the public
• block-level permissions

Story

• your team maintains a graph outlining all your development plans for your platform. You have varying level of permissions to:
  1. not overwhelm your investors with too much information
  2. maintain a private team development workspace
  3. coordinate input from stakeholders both internal and external to your company
  4. share road maps with the following views:
     1. internal development team
     2. investors
     3. maintainers
     4. contributors
     5. general public
• there exists another graph maintained by the community capturing what they want to see in the platform based on actual experience.

Opens

As platform maintainer, how does dev team integrate their internal priorities with public demand?

What level of transparency?

How does reputation fit into the picture?

How are differences in opinion resolved?

How does the platform foster a collaboration model & public graph that persists even after the platform fulfills its original purpose and the tool is no longer maintained? How does the handoff to the public happen?