MeebitsDAO: How We Work
- Part 1 — Introducing: MeebitsDAO
- Part 2 — Structure, Governance & Roadmap
- Part 3 — Voting Tokens, Membership Tokens
Building the Metaverse, bit by bit…
We’re here because we want to build cool stuff. We want to have our Meebits running around in games, VR chatrooms, AR live events and applications we haven’t even imagined yet —
5 years from now we still want to be using our Meebits as avatars in the open, interoperable Metaverse!
…but there’s a lot of hard work that needs to be done.
The early developer community has already started to gather in our private Discord (soon to be made public) to discuss how to create the essential building blocks we’ll need to use to develop more interesting applications.
MeebitsDAO is a development hub.
This is the purpose of the DAO, which is simple in a sense — we exist to enable (and fund) developers to make things using Meebits.
Common goals & sponsored bounties
Part of the DAO is enabling the community to build what they want to build, but the real potential exists in our combining our efforts to chip away at larger problems and to work towards common goals.
MeebitsDAO is a development fund.
Time is precious, so we want to incentivize the community to work on projects that we initiate as a DAO, but equally we want to create a structure for entities to sponsor bounties that define specific projects to work on.
We also want to make sure we find the right balance of what is right for the community and what is right for sponsors, which may have commercial intentions beyond what the DAO will develop.
Everything the DAO builds will be open source licensed.
It seems appropriate that the community fund should develop resources that the community can use, so while projects may be sponsored, the deliverables must be returned to the common repository — at least to be accessed by the DAO itself.
The RFP process — How projects get initiated
To provide structure around our projects, all projects will start with an RFP (request for proposal) memo that will define:
- The Brief — the request from the RFP sponsor
- Milestones & Bounties — Checkpoints & incentives for completing the parts of the project
- Timeline — Due date for proposals, and timeframe for completing the project
- Acceptance Criteria — The final steps-of-doneness for the sponsor to approve the final deliverables as completed
RFPs will be written in consultation with the DAO to make sure it fits within the overall charter, and larger RFPs may even be voted on.
Team proposals — as a response
In response to the RFP, a member of the community should lead the response, and write a proposal outlining an approach to completing the project, or one of the bounties.
The proposal should consist of:
- Team lead — There should be a single point of contact, even if the team consists of multiple members. The team lead will be responsible for distributing the bounty, as appropriate, to the rest of the team and delegating roles and responsibilities.
- Team members — One of more person who will be working on the project, this could be the expected number of people, if team members still need to be recruited.
- Summary of plan & approach — What the team will do, how they will do it and within what expected timeframe.
Multiple proposals & Sponsor approval
Upon receiving proposals by the due date for the RFP, the sponsor will choose whether to accept the proposal. In the case where multiple developers or multiple teams want to complete a bounty, and write separate proposals, the sponsor will choose a single proposal and team to move forward with.
What do you think about this model of sponsorship?
Everything here is a work-in-process — DM us on Twitter with feedback @MeebitsDAO — start shaping the community now with your advice & opinions!