Audience: any decentralized organization, and people who want to be gainfully employed as web3 workers. People who want to be getting organized as a result of the conversations they're having together.
About the Done Collectively Platform: DAOs on Cardano (and EVM?) want to have a place they can go to be organized together. Organizing into groups, getting those groups commissioned (with tokens or spendable coin), forming project plans, writing project Bounties, and engaging with communities are all on-mission. The present version of the application also facilitates transparency around mission, vision, values and other cultural and execution-oriented details.
James at Gimbalabs said, "Navigating all of my multiple DAOs and feeling organized about the experience? … aw, f*** yeah!". Dan Mercurius said "it's like a more clear / coherent version of what I tried to do with Zenhub". George Lovegrove said "make[s] it nice and easy for people to move their way inwards toward full time contribution". Tom (TCT) of ADAO said, "It is the platform that is going to make Cardano THE blockchain for DAOs. [it] will allow ADAO to onboard new members and contributors efficiently and effectively."
--------------------------------------------------------
Please see our intro paper and find project updates at:
<https://drive.google.com/drive/u/0/folders/1ASarfs9YaJYbORxMIDSC3I38nTrQc8IA>
-----------------------------
THIS PROJECT PROPOSAL:
-----------------------------
Done Collectively will already have places for DAOs to write up tasks and bounties for them. DAOs will be able to "send out the bat-signal" and bring in new contributors they need to get their missions done. This project will aggregate bounties from many DAOS and make them accessible to bounty hunters.
People seeking bounty work will be able to filter that list of bounties based on skills-match and possibly other factors, getting good project matching and saving themselves time trawling through old stuff they don't want to see. These sound like "table-stakes" features, yet most bounty boards we've been able to find don't have anything of that sort. Same way with being able to click through to see more context about the teams and projects who are sponsoring the work.
The internet of DAOs and the internet of jobs is likely to be the future of work. It enables self-actualization for web3 workers and people who have wanted to shift that direction. Most existing bounties on bounty boards found across all chains are highly technical, and lacking much in the way of context. It's hard to tell how to start collaborating with the sponsoring teams.
We seek to change all that, enabling bounty hunters to easily find the project, the context and the team. We want to enable a quick start for getting into the delivery of value to projects.
—–– More about upcoming integrations with Done Collectively ——
On our roadmap are such projects as:
use github-like semantics (or github itself?) to administer the co-evolution of those details, with strong traceability built in, and bridging to Gitbook is contemplated as well. We're ready to build in Discord integrations, so that Groups, Projects, Bounties, or just about anything else in the platform can come with side-chat in our communities (with backup/snapshots of those chats imported into the DC platform as a bonus).
Perhaps our most exciting product plan is the integration of token-based signaling directly into the governance workflows in the application, enabling hundreds and thousands of DAOs to start moving more quickly together while integrating feedback from community and contributors, and including tokenomic results to create financial ecologies for any of our DAOs who would want that.
A great bounty-board for the Cardano developer community will facilitate collaborations, enabling new community members to quickly find their way to projects needing their help, and support our development projects with bounties for other contributing roles.
This project aligns with Support structures and Incentivization structures as mentioned in the challenge brief's "potential directions"
One of the main challenges for a great bounty board is for it to be actually useful for the people who show up looking to add value to a project and earn money for it. We are positioned to improve on the typical web3 bounty board in at least one major way in the short term, by connecting those bounty hunters directly into the working groups and projects, and review their missions, their clearly expressed goals, plans and success criteria. This will already be a major advancement over today's typical bounty board, and give a person enough good information to start engaging meaningfully in live sessions with project teams.
Having good filtering to serve bounty hunters is another relevant challenge. That's primarily because of dependencies on effective skill-and-certification frameworks. As we're currently planning work to enable DAOs to express their skill needs, we'll soon be in a good position to add great filtering capabilities to serve bounty hunters.
--- more generally…
Scope risk would normally be a critical consideration for a project such as Done Collectively (our platform mitigates that very effectively; see also technical risk below). We've been able to scope all of our Catalyst proposals to be narrow, building directly on product functions already present, so that when our moment is right, we can dig in with laser focus and do just this one thing.
Staffing is probably our greatest general risk. We're relying on existing partnerships and relationships (Gimbalabs, ADAO, Web3:4Life) to assist with the project in any areas of graphic design, market research, technical collaboration or anything else that comes up. If many of our proposals are funded, we may distribute some of the efforts over a longer time interval, with highest-value work queued first. With that funding, we'll also be positioned to hire trusted developers and other contributors from our existing networks.
Technical risk is naturally a key consideration for such a project as this. That said, our application framework has been under continuous development for some years, in the context of developing a software-requirements-management product and a relationship-management SaaS product for churches. New features are typically quick to create and work very reliably.
Our approach on the design and implementation of our platform has always been to enable the highest quality and production-grade results even from projects executed on prototype-like timelines. Our current product, still in late-alpha after just a few weeks of part-time development effort, is being urgently requested from teams who see its workflows, even as those workflows are still in active design & evolution. This speaks to the effectiveness of the platform, and also our collaborative process of finding shared meaning and reflecting it in useful application workflows.
Our platform includes facets of deployment-management, system-operations, lightweight virtual private networking, decentralized system operations, and SaaS infrastructure. These details mitigate operational risk, helping to ensure we have good support for production-time practicalities.