Please describe your proposed solution.
-----------------------------------------------------------------------------------
Overview
Over the last few months tools like dework have become adopted enthusiastically to meet a demand for Web3-native project management with token payments, credentialing, and bounties.
Tevo Saks has started an initiative to facilitate a review of community use of dework. This is building a useful comparative process framework. Already this activity has revealed a wide range of requirements from bounties and voting to GitHub integration for audit trail. As well as many different process approaches that reflect particular community needs, priorities and values.
No one size fits all. Whether we build decentralized nodes or grow distributed networks it is important to capture the varied use cases that emerge.
See Tevo's Miro - https://miro.com/app/board/uXjVOs6bN2M
-----------------------------------------------------------------------------------
The Problem revisited
The problem is that existing process frameworks are modeled on specific dApp platforms. The efficiency of a consistent single centralized process relies on specific interests, set functions and prescriptive roles or paradigms.
-----------------------------------------------------------------------------------
Solution
In contrast, effective decentralized governance is dynamic and flexible. This is an important adaptive response to the inevitable and opportunistic gaming that occurs in a complex network. The decentralized nodes of our ecosystem rely on an evolutionary system "where rules are able to change continually to avoid threats and seize opportunities" - Calcaterra, Craig; Kaal, Wulf. Decentralization (pp. 284-285). De Gruyter. 2021
To nurture this environment it is essential that community nodes are documented, compared and continually assessed. Tevo Sak's work on ecosystem framework is one contribution to this task (see video Innovation Fund Research Overview). Stephen Whitenstall's documentation and auditing is another (see QADAO GitBooks).
Dework Process Framework Workshops
<https://www.youtube.com/embed/FX4LUCYBvVg>Tevo Saks has started and is progressing Dework Process Framework Workshops with participation from across the community. Incl. SingularityNet Ambassador Program, Catalyst Swarm, Community Governance Oversight, Governance Services Guild (former CC Admin), everCrypt DAO, Cardano4Climate and Catalyst United.
This is supporting users who wish to start using dework, to see how its functions may be related to their own projects. So a user may understand what role the tool may play.
To continue and incentivize this work bounties will be posted via Swarm.
dApp requirements analysis
Now an opportunity exists to conduct a requirements analysis for a general project management dApp framework. Real world use-cases of project management dApps such as dework (<https://dework.xyz/> ) will be examined to identify their characteristics.
This will provide a snapshot of the use cases of various community nodes. What do they have in common and what differentiates them. Traditional requirements analysis will elicit, record and analyze according to a given perspective or context. And more recent Agile approaches may scope use cases in terms of user stories in an attempt to naturalize requirements in everyday language.
Our approach will be more intuitive, reflexive and experimental. Broadly it will fit into gimbalabs Project Based Learning approach.
Open dApp Framework workshops - Project Based Learning
Project Based Learning (PBL) is a "learning by doing" approach that preserves current knowledge and perspectives. Support is provided on a mentor basis in order to realize solutions to real world problems.
Building on Tevo's work, we intend to do a functional analysis of the common use cases and consider various abstract models or design patterns that may be used in specific circumstances. This would examine functional requirements such as bounties, tokens, voting, tasks, roles, contributors, and technical requirements such as communication channels, audit trail and wallet connection.
In the PBL context, the functional analysis is not prescribed. The intent is to discover use cases as they exist.
Decentralized governance analysis
In addition, blockchain governance principles and maturity models will be referenced to determine how decentralized the project management dApps are seen through these lenses. We will reference standards such as IOG’s Blockchain Governance Principles paper and the draft Blockchain Maturity Model.
Tokenomics PBL Curriculum Development and Building Background Knowledge: (BBK).
In collaboration with gimbalabs, the functional analysis, abstraction and decentralized governance analysis will be fed into Project Based Learning modules on the Canvas platform. Functional and technical requirements will be documented, and possible Cardano solutions identified in Plutus. This may take the form of cross-referencing or connecting with existing PBL modules.
Finally, the Open dApp Framework will form the basis for modules in Tokenomics PBL Curriculum Development and Building Background Knowledge: (BBK).
Please describe how your proposed solution will address the Challenge that you have submitted it in.
-----------------------------------------------------------------------------------
This proposal specifically address the Technical requirements section of the F9: Dapps, Products & Integrations challenge.
The right tools ?
In order to see whether the Cardano ecosystem has the right tools, libraries and SDKs for a particular idea it is useful to have a high level model of user requirements.
Our workshops will examine common use cases from a range of projects currently working in the Cardano ecosystem and seek to identify what typically needs to be in place for a Project Management dApp.
Materials from these workshops will be fed into Project Based Learning modules to create a reference product which developers, users, toolmakers and maintainers can draw on real-world use-cases to help them build feasible and relevant products.
What are the main risks that could prevent you from delivering the project successfully and please explain how you will mitigate each risk?
-----------------------------------------------------------------------------------
Insufficient interest in an Open dApp Framework
-----------------------------------------------------------------------------------
A major risk to any project is insufficient interest in the problem it is trying to solve.
-----------------------------------------------------------------------------------
Mitigation
-----------------------------------------------------------------------------------
Based on workshops already held we believe there is a great deal of potential interest in an Open dApp Framework and a ready user base for Project Based Learning materials.
To promote interest and engagement we will also be using Swarm bounties for incentives.