This is in part my direct response to @willblackburn’s post above (I pretty much entirely agree) and the DAO canvas PR.
- To emphasize what was said above, I want to call out the goals organization: the 2 bullet organization will help keep things tightly focused (subordinate points support the mission defined at the top level).
- Anything that we do should be able to trace its way back to one or more of the bullet points, top level more desirable than lower level
- Operations is a necessary evil that’s not on that list, so things like maintaining a treasury, etc, will have to be given weight (or even priority) depending on what we’re trying to address.
Now to address the DAO Canvas
<wall-of-text>
- Diversity, Inclusion, and minting literally anywhere other than ETH Mainnet: I think that if we choose our seasonal NFTs to be on not-ETH, we’ll be able to get more people in that would otherwise not be able to mint. Also will be a good learning opportunity / source of content (aspiring to the level of the original NFT as solidity smart contract content).
- I have 2 thoughts on treasury
- Can we get a partnership with a DeFi DAO for some kind of vehicle to maximize ROI for our undeployed assets
- Can we open up a vehicle for staking-for-the-DAO in which anyone could stake assets to the DAO, which could then deploy the assets and (per the contract) keep the yield on that staking? This implies that the end user has a contract (and reasonable human) assurance of being able to pull their stake as desired.
A common thread that I see in projects discussed (education, resume building/maintaining, job board) is tied to the identity of the user, data (manipulable) about the user, and data (tokenized, immutable) about the user. Based on what I do know, that looks a lot like an application of Decentralized Identity; right now I’ve been looking at Ceramic and IDX but I’m sure there are other tools, but the crypto world is well set up to handle this: you “are” your wallet, you have a DID tied to that wallet, and for hard proof-of-work you could have NFTs or oracle-verified off-chain proof that would then be captured as NFT. Just my two cents and would require more work, but I think that this notion of ID is going to be real important.
Season 1: Perhaps just identity?
- Education is going to have some challenges, in terms of good curriculum design, that I think most of us don’t deal with frequently (typically it’s me that knows less than my compiler, etc)
- Both Job Board and Education lean heavily on encapsulating the attributes of a person in terms of achievement/completion tracking.
Boosting each others content: as we saw from the Write Race this week, our community is large enough to make a pretty big impact if we all throw ourselves at something. Boosting fresh content via our individual accounts will help juice anything any of us publish (pending some clever anti-human-boosting that’s in place on a given platform).
DBUCKS pronounced “DaBucks”? Or we go american old-west and refer to money as Bits… DaBits? In both cases, of course, taking that soft “a” so it’s not that far from the “de” in developer. Definitely not playing off anyone’s name.
I think new proposals per week is a dangerous metric as the people that then have to read them would be getting swamped (boost those numbers)
I’d instead focus on tracking milestones inside of proposal completion, or other conventional code velocity tools (but I don’t work at a BigCorp so I can’t speak very intelligently about those)
Caps and Global Constraints: We are obviously capped at 8000 D4R tokens (at least in the original issue); my take is that these are the OG members and permanent. Perhaps we get some in treasury to hand out for outstanding performance as a Season member. In general we want to make people want to be in the DAO - and OG D4R is the way to do that → OG D4R token should be desirable.
Legal Strategy: We start doing things for money, we should probably have that settled. Pending any major developments, it makes Wyoming’s DAO LLC structure appealing in the US - but I’m not a lawyer.
I would like to make sure that as we define personas for web3 education and collaboration we keep in mind the Entrepreneur persona (job boards too, but that might be a less likely use case)
And, as a DAO of developers, we ought to pay attention to anything that we build: is it something a non-technical DAO would use, and can we package it as a RedHat $$$ for opensource software deal if so?
</wall-of-text>