---
# System prepended metadata

title: WGMI Notes

---

# WGMI Notes

**Matt:** Organizing hackathons, managing open source development



Send technical decks how to build on DAOhaus.


**Ven-**
First: Focus on the why & specific use cases
Then: Community support.  Devs hang out with other devs. 
Who: People to build for.

**Jord-**
Cold start problem: They have the idea <linked></linked> to experts.

**Ask developers** already in the ecosystem what they would like to see from DAOhaus. What they would like to spend time building. 

**MattWright.eth:**
Hackathons.
Community calls. 
Host various workshops.
Fork the repo - plug in api.
Systematic & methodical with how they're growing engagement.
Activity to convert them to a contributor or an integrator.
Listening to community as numero uno.
Do they know what they can build? If so, do they have the resources?

**Piloting with a small group**
Cohort system - small pilot system
Might be able to inform others & get them excited
Troubleshooting & Community management to others in that cohort. 
Case Study the first cohort - they'll feel cool they were first.

**Ambassador programs**
developer evangelism program
Find DAOhaus rockstars who are technical & understand things (like shaman, etc)
How do we incentivize them
Rapport in community, access to core dev team

**Say you get 5 people** who are DAOhaus evangelist. Get them on calls w/engineering team once a week. 
- "Here's how you deploy the shamans, here's how you can build about it"
- Put out a tutorial video, interesting ways to portray
- Host workshops, talk to community members, drive them to push code
- If you get people to do that, some other set of incentivies. 

**Pipeline for feedback** on bug fixes
    Technical product managers - dev focused people tend to fill in those gaps.


**Jord**
    8 Packages - remix & rebuild DAO interfaces.
    A lot of communication about that. 
    DAO application from scratch - turning that into something devs do for fun.




