This proposal seeks to establish Academy as a sub-DAO of Developer DAO, based on the current DAO Governance Structure.
Academy is an educational platform for builders, seeking to onboard members and the wider public into both the DAO and the broader web3 industry by providing quality content, support, and a great user experience. An MVP is available today and this proposal considers its next iterations.
The Academy team works to fulfill the main mission of Developer DAO: to educate and onboard web3 contributors. What started as a study group has evolved and grown into a full effort to build a free and high-quality platform to empower builders to make an impact in this industry.
The Academy team is building a free education platform. Prior to this budget, an MVP has been designed, developed, and deployed. Since the MVP, new team members have joined and design thinking exercises have been facilitated to explore a roadmap from here.
The updated member experience will focus on one persona: the web3 Learner - persons willing to enter the web3 world by improving their skills. This aligns with our mission to “Accelerate the education and impact of a new wave of web3 builders.”
Academy is to be a sub-DAO of Developer DAO, and as such, intends to operate with a flexible and autonomous structure that allows for experimentation and iteration.
As a team, we task ourselves with delivering and maintaining a robust and meaningful web3 education platform. Together, we have combined decades of professional experience across web development & architecture, education & pedagogy, technical writing, product development, and design. Starting Stewards in those core areas:
Product & Design: Erik, uma
Development: 7i7o, brianfive
Pedagogy & Content: piablo, john-mac.eth
The specifics of how each domain performs its functions will be documented along the way as best practices are discovered. Further, there has been and likely will continue to be significant domain crossover between individuals in these roles.
These Stewards will be signers on the Academy multisig and the sub-DAO will operate in Season 2 without a separate entity, under The Developer DAO Foundation, abiding by relevant requirements.
Any member of Developer DAO can join weekly meetings and apply to take on bountied tasks.
|O2||Provide DAO members with high-quality learning opportunities||Owner|
|KR||Enable users to store their progress||Development, Product/Design|
|KR||Research and design v2 of the Learner UX||Product/Design|
|KR||Implement and deploy v2 of the Learner UX||Development|
|KR||Facilitate discovery of and document Operational Framework||PM|
|KR||Include learning objectives for each lesson||Pedagogy/Content|
|KR||Develop learning standards for all lessons||Pedagogy/Content|
Team Stewards: Monthly Individual: 600 / Total for the Season: 16,800
Reward Pool* for Contributors: Monthly: 8,400 / Total for the Season: 16,800
Total request of CODE for Season 2: 33,600
Total request of USDC for Season 2: $0
Note: Steward contributions have been ongoing since Season 2 inception, so all four months are budgeted to include retroactive reward. The reward pool monthly request includes only the final two months of Season 2.
Bounties eligible for the reward pool will be determined by the Stewards throughout the Season. The process of defining tasks, assigning value, and assigning task owners will be defined, iterated on, and documented during Season 2. Any D_D member, including Team Stewards, are eligible for reward pool tasks.
We commit to transparency of allocations and will maintain those in a publicly accessible location. Further, any reward pool CODE not used will be returned to the DAO Treasury at the conclusion of Season 2 or incorporated into the next budget request.
As a sub-DAO of Developer DAO, Academy will operate as a separate, autonomous organization.
Content will be prioritized for the platform in two ways:
- Internally-driven: the team will assess what it believes to be a well-rounded and high quality user experience, then create tasks to achieve that end.
- Sponsor-driven: the team will assess opportunities to add partner content to the platform for a one-time and/or ongoing fee, then create tasks to achieve that end.
The process for each will be another iterative process that gets documented as they’re refined in Season 2. The team is committed to finding a healthy balance between homegrown and sponsored content, acknowledging that revenue is required to be sustainable, but that over-prioritizing sponsored content may result in a lopsided product.
The Academy team endeavors to robustly invest in its foundations, allocating a third of net proceeds (defined as revenue minus expenses) back into Developer DAO (22%) and into the Academy multisig (11%). The remainder of net proceeds will be distributed to Academy contributors proportionate to the distribution of CODE.
An example: $1000 revenue - $100 expenses = $900 net proceeds. 22% ($198) goes to D_D, 11% ($99) to Academy multisig, and the remaining 67% ($603) is divided amongst the contributors during that period based on the CODE distributions (Steward role + task completion).
A notable omission is a reward to Partner Leads that facilitate deals with sponsors. Once a sponsor onboarding process is defined, and the demands of Partner Leads are clarified, will the team work with Partner Leads to agree on and document an appropriate reward.
The team will continue to build an education platform, helping Developer DAO to fulfill one of its core missions: providing free education to web3 builders. Academy is an open source public good, available to learners within and beyond the walls of D_D.
In addition, Academy will allocate 22% of net proceeds back to the Developer DAO treasury, recognizing the importance of the DAO as the primary source of contributors and learners, and as a message amplifier via the power of its brand and following.
The DAO’s Treasury would allocate 33,600 $CODE tokens to the Academy multisig over the course of the Season.