[IMPACT]
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:
—––––––––––––––––
Nearly every element in the Done Collectively platform will be governed through a lightweight process, allowing DAOs to make their way at the speed of trust through finding Mission, Vision, Values, Working Groups, Projects and other organizational details.
Each of these is a place where a chat conversation can start. Adding discord integration to Done Collectively will enable them to automatically have channels & threads in the DAO's Discord servers, where chat conversation is normally done. Those conversations will be imported back to Done Collectively, where many other organizational details are easily found. The Discord chat archives will augment the other organizational details found in the DC platform, and be displayed only at the time and place when they're relevant to DAO users' activity.
This will help people by removing the need to add another real-time messaging tool to their life. Instead, they can simply use the individual tools that are relevant for their most important work. The integration will help them easily transition between DC and Discord channels while staying out of their way.
—–– 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.
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.
This proposal is specifically for integrating Discord, perhaps THE most ubiquitous application people use in Web3. This aligns directly with 3 out of 4 guiding questions from the dApps and Integrations brief. "What are the key applications that underpin the application ecosystem on other platforms?", "What are the most profitable or most used applications on other ecosystems?" and "What applications deliver the highest amount of value with the least amount of technical sophistication?". Integrating with Discord is an obvious answer to these questions.
We'll integrate with the DAO-managability platform described by Tom (TCT) of ADAO as "THE platform for DAOs". While that quote is a bit forward-looking, it is our intention to provide tooling that will be leaps and bounds ahead of what is currently available for DAO management on ANY blockchain.
From the brief: "what does success look like? > Novel and viable applications get built of top of Cardano attracting users. Integrations manage to pull in more adoption."
… we believe this proposal and our project overall will very effectively respond to both of these.
––––––––––––––––––––––––––––
Please see our intro paper and find project updates at:
https://drive.google.com/drive/u/0/folders/1ASarfs9YaJYbORxMIDSC3I38nTrQc8IA
Effectively engineering the linkages between platforms is the most important outcome here. It's good news that Discord's authentication, 'bot user, and other automation capabilities are very strong, with detailed permissioning, so that we can provide appropriate constraints and permissions so that our integration can do all and only what it needs to create any channels and threads.
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, released incrementally, 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.
[FEASIBILITY]
In general, the Done Collectively platform is well underway. Building out additional components such as proposed in this project will leverage everything already in the platform, and we'll build this increment according to this ROADMAP:
The implementation plan for this includes:
Month 1:
- Create a simple discord bot
- Add an Connection workflow to the application, in a place focused on DAO-administration
- allows a DAO on the platform to grant access to their Discord server,
- checks that the granted role has sufficient permissions
- allows selection of channel-groups in which the 'bot will have permission to create new channels
- allows selection of channels in which the 'bot will have permission to create new threads
- Add a Bridge To Discord workflow within the application, where sufficiently privileged DAO members can choose from existing discord channel-groups or message-channels, and select for creation of a new channel or thread for any given Project, Working Group, etc.
Month 2
- Implement webhooks / other 'bot connectivity mechanism to monitor for new & edited messages in channels & threads. This mechanism will archive the message content so that Discord doesn't have to be the sole, proprietary data-store for the archive of important conversations relevant to DAO governance and workstreams.
- Display discord messages in-app, at the places where they're relevant
Continuing followup as needed for maintenance, refinements, product-support questions and any needed corrections.
Key results of this work will be:
Done Collectively DAO admins and Discord administrators can connect the two services together.
Users of the DC platform will have threads and channels created for them as & when the time is right, suited to the lifecycle stage of a proposal, working group, etc.
People in Discord can click through from those threads & channels to publicly-visible (or appropriately permissioned) places in Done Collectively and see the bigger-picture context & organization
People in DC can click through to Discord for chat activity or simply review the chat log right there in the DC app.
Using a standard rate of $100/hr for skilled contributors.
Project Management:
4h/w x 8 weeks = $3200
Software Development ('bot)
16h/w x 3 weeks = $4800
UX Design: $4000
25h = $2500 - administrator connection sequences
15h = $1500 - connecting DAO elements (proposals, working groups, etc) to discord channels & threads
Software Development: (application integration) $10200
48h = $4800 - administrator setup, connection and configuration
36h = $3600 - in-app UI & server-side work for channel/thread creation
18h = $1800 - presenting chat archives in application
Total: $22,200
Randall Harmon - software developer, application architect, Swarm Veteran, Gimbalabs core contributor, facilitator. Will manage the project, implement most of the UI, and provide guidance and any needed technical mentorship to other contributors. https://www.linkedin.com/in/randall-harmon-aa52765/
TCT (Tom) of ADAO - a great practical collaborator, he'll provide on-the-ground feedback on integration details, QA help and general project management.
Gimbalabs Tokenomics PBL team: they're focused on tokenomics for the Gimbalabs DAO, plus all the stuff that goes along with it. They'll also help with market-fit and UX evaluation
Javascript developer / Discord bot integrator (TBD): will likely be sourced from current ADAO or Gimbalabs community
[AUDITABILITY]
Number of Discord integrations connected to DAOs on the platform
Number of channels created or connected to for Projects and Working Groups in Done Collectively
Number of threads created for governance proposals in Done Collectively
Number of new DAOs created in the Done Collectively platform
Number of messages replicated from monitored channels
Latency in milliseconds between Discord and DC
The key success criteria for Done Collectively is that we're delivering the things most important for decentralized organizations to get things done together. That includes many or all of: getting and being organized, reflecting to each other transparently what plans we figured out together, creating good incentives for that work to be done, mustering resources to ensure those incentives have meaningful backing, and showing clear credibility signals to support both trustability and due caution to would-be DAO members.
For THIS PROJECT:
People at DAOs (with Discord administrative permission) can easily connect Done Collectively to their Discord server)
People in DAOs, proposing new Projects or Working Groups, easily spawn new conversation threads in their discord servers
People in Discord can easily click through to the relevant locations in Done Collectively
DAOs in Done Collectively get archival copies of important message content from Discord
When people are chatting in governance-relevant threads & channels, their comments appear in near-realtime in Done Collectively.
New proposal.
