Developer DAO: mandates & deliverables

Mandates: Builders first
- Support: resolve daily issues on forums & channels, drive weekly meeting agenda
- Bounties: prioritize bugs & features w/ task management & contributor retention
- Advocacy: hold workshops & events, content marketing with talks & blogs


Election Format

What does the election format look like? Thinking in terms of number of positions, voting procedure, etc.

Thanks for all you do!

@Validity I’m fleshing this out right now. I will share thoughts shortly.

1 Like

Hi @giv Solidity dev here, building NFT, DeFi, DAO dapps…Keen to join Harmony Developer DAO…Please keep us posted how is it progressing.
Regards, Sanjeev

@sanjeevkumar761 please see my post above.

Mandates for the Developer DAO looks great!
Well done!

1 Like

The urgency to build DAO’s as a target displaced the team & community’s priorities on how prospective DAO’s should functionally look like as an org structure, how renumeration and priorities need to be decided.

People > Knowledge > Process > Pipeline > Product sitting atop the constant feedback layer is backbone of DAO’s framework, internally & externally for facilitating tools & incentives.

There are a lot of example structure proposals you’d find in the wild (No surprise, they have existed before).

The Bankless DAO’s Guild will do nothing but help in horizontal integration across different business functions (i.e. marketing, ops, developers).

Planning & preparation is half the battle - I know that some work was going on across different domains, but the complete process had no structural order to it.

As stated months ago in Reddit forums, hiring an org consultant internally could have saved so much trouble because this isn’t reinventing the wheel tbh, especially for community guidance across the complete framework.

This is how a lot of Fortune 500, Big 3/Big 4 consultancy firms have actually worked — for almost 7 years now as far as my experience goes (seeing HR transformations).

On a closing note, Web 3.0 is an incremental process improvements to existing work models that have persisted over many years - We are reinventing the wheel in a sense of moving from iPhone 7 to iPhone 11, but it’s the UX is what is meant to incrementally change the future of decentralized workspaces (i.e. permissioned privacy, choosing tasks, flexibility & negotiability in wages & contribution oriented
proprietorship & community-supported liability protection) in a meaningful way.

All this, in the backdrop of difficult national labor laws & a de-globalized world. You can still do it - But it will always require having a product centric thesis with positive nudges for customers, that permeates from top to bottom among tiered competency circles, for those relatively marginal, yet effective gains. Not just algorithm based, but human assisted curation as well.

Yes - It still takes a lot of work because it is a compendium of immense accrued value that traditional firms have created post Industrialization era, at almost breakneck pace (eg: This is Amazon’s micro-services architecture Deathstar i.e. 50 million code deployments every year)

TL;DR : Bring in some specialists. Having “small teams” will not cut it, because it results in poor visualisation of the problem statement you want to fix.