Roadmap
This is our plan for the Osmosis Community Support DAO and the steps needed to accomplish it. It centers around mission-critical business objectives and documents progress towards them as we go.
Vision
The OCS DAO aims to build and drive a sustainable, effective community support system that solves the most critical challenges facing the community.
Our mission is to bring together the needed people and resources to provide excellent support service. We aim to encourage and incentivize the community to become increasingly involved in determining the project's future by embracing governance and rewarding people for making meaningful contributions that fulfill the Zone's support needs.
Lastly, we want to foster channels and spaces for the community that are conducive to a healthy, productive dialogue and exchange of ideas. This means contributing valuable insights for new features, solutions, and innovations in the interest of increasing demand for OSMO and attracting investors to the Osmosis AMM.
Core Objectives
1. 🧠 Evaluate community support problems, research effective solutions, and make critical decisions; occasionally (more during the start-up phase) bootstrap our own solutions when no good 3rd party option exists; rarely, engage key stakeholders regarding governance matters posing an existential threat or safeguard to the community
2.💰Negotiate payment and distribute funds from a multi-sig wallet to solution providers, whether they be qualified community members or outside vendors
3. 🤝 Actively participate, with the support managers, in the selection of community administrators
4. 👀 Guide projects and track contractors' outcomes to ensure that they fulfill their commitments
5. 🧪 Work with the Marketing DAO and other partners doing tooling and contract work to ensure our efforts are synergistic instead of redundant.
6. 👂+ 🎯 Conduct periodic meetings with the core team and community to share progress, gather feedback, and ensure everyone's efforts are aligned.
7. 🗣 Write, present, and report findings and results in select media.
Legend
Action 🔷
Any item preceded by a blue diamond 🔷 with blue text is a 'key' action. The ground truth about milestones and capstones is that there are often considerable distances between them. It may take a combination of baby steps and big leaps to get from one to the other. We will not list all of these actions, but will try to highlight meaningful ones.
Milestone +
Milestone, an important observable solution or resource that benefits a large portion of the community, often marks progress towards a capstone; marked with regular purple text and a plus sign +.
Capstone 🟪
A capstone is a major meaningful outcome resulting from code and/or critical consensus building. It comprehensively improves user experience throughout the Zone. It's in bold purple text, preceded by a purple square 🟪 .
Canceled
Canceled objectives may occur. If we deem a goal and its circumstances have changed drastically – or just enough to make an investment in time and resources unfavorable – we reserve the right to nix it. Sometimes what you don't do matters just as much as what you accomplish.
Timeline
2021
Q3
September
Q4
October
November
December
2022
Q1
January
February-March
Q2
Q3
Q4
Last updated