# GM 1.6 - Ratify Working Groups and Responsibilities


*As new ideas emerge, contributors are encouraged to propose new guidelines and amend existing ones.*

### **Author:**

Nodallydude

### **Proposal date:**

February 10, 2022

### Summary:

**Proposal Principles:**

1. Working groups are clear and transparent. Meaning, anyone can read what’s going on, and anyone can join any team. 
2. Working group roles are defined. Meaning, we know who to go to or request help from when something is needed. 
3. Working groups responsibilities are clear. Meaning, work outlined in responsibilities are not inhibited by a need to vote (with the exception of use of treasury assets). 

 

Through the first few months of the DAO a few key work streams have emerged, this proposal will help define our foundational working groups, what their roles / responsibilities are, and who are the individuals within the working groups as well as who are the leads within the groups. 

In this proposal **roles and responsibilities** are those tasks which we are empowering the working group to complete **without a DAO vote, except in the case where treasury funds or assets are required.** 

**Team Definitions —** Team leads are responsible for outcomes, and represent the DAO’s point of contact when help is needed or an issue needs to be resolved. Team members are similarly responsible, and help with the overall workload.  

### Risks:

- Potentially too much structure for where we are as a DAO right now.
- Reliant on key team members.

### **What are the changes being proposed?**

We propose the creation of the following working groups and associated responsibilities:

**Governance**

- Roles and Responsibilities
    1. Administration of governance
        1. Ensure funding cycle calendar, DAO Proposal, and all associated Governance process pages in Notion are up to date.
        2. Keep us on the funding cycle calendar. 
        3. Shepherd Proposals through the [governance process](https://www.notion.so/gm-DAO-Governance-Process-3e3dfa72b89448d69b6c27bde31b790d) by setting up temperature check polls in Discord, Publish and alert about Snapshots, and handoff execution to the multi-sig signers when votes are at consensus. 
        4. Activate urgent or emergency governance process. 
    
    | Team Lead(s) | Team Members  |
    | --- | --- |
    | 0xSTVG.eth | Nodallydude |
    | De-Fi Beats | Ze-Boubs |
    | Cyphr | sloth |
    |  | Arnearnearne |
    |  | ChaLong |

**gm Studio**

- Roles and Responsibilities
    1. Front end development and Back end infrastructure development.
    2. Smart Contract deployment.
    3. Development tool administration (ex. Github  or AWS).

| Team Lead(s) | Team Members  | Team Members  |
| --- | --- | --- |
| Willyham | bhosh | Coelcanth |
| cxkoda | itsreal | Ereska |
|  | iamalpaca | Froze |
|  | 0xraian | jjnnbbtt |
|  | Ben |  |

**Curation Panel**

- Roles and Responsibilities
    1. Curation Administration:
        1. Receiving Studio Applications and removing identifying information, presenting to curation panel in Discord for feedback, running go no-go poll, and then responding to the artist with summarized feedback.
    2. Implementing process workflows to streamline submission and feedback process. 
    3. Handing off accepted artists to gm Studio team. 

| Team Lead(s) | Team Members  |
| --- | --- |
| Cyphr | Panel Here |
| Nodallydude |  |

**Tokenomics**

- Roles and Responsibilities
    1. GM Membership Token distribution. 
        1. Distributions to individuals who may help the DAO (artists, investors, operations specialists, etc)
    2. GM ERC-20 (or similar) token development. 
        1. Utility, Distribution, creation. 

| Team Lead(s) | Team Members  | Team Members  |
| --- | --- | --- |
| calbear4life.eth | Tree (ImmortalTreearms) | ChaLong#8246 |
| Coelcanth | a_dirty_boy#3393 | SpookyOrbit#8939 |
|  | mostlyrandom#0001 | PRO_RW0#1241 |
|  | sofaws#7342 | coloredG#6930 |
|  | Ze_Boubs #5211 | InsideTheSimulation#9285 |
|  | Hobbes#4315 | Speeps#6763 |
|  | arte.tez#0698 |  |

**DAO Investments / Biz Dev**

- Roles and Responsibilities
    1. Artist outreach for Studio applications. 
    2. Partnership conversations and agreements between our DAO and outside entities. 
    3. Capital allocation or pooling for specific investments. 
    4. Capital allocation for good! 
        1. Example, carbon offset or donations. 

| Team Lead(s) | Team Members  |
| --- | --- |
| Cyphr | TBD! |
|  |  |

**Content and Marketing**

- Roles and Responsibilities
    1. GM Gazette publication.
    2. Social Media presence (Twitter, Medium, etc).
    3. Giveaways.
    4. Appearances and Representation — Podcasts, Articles, etc

| Team Lead(s) | Team Members  |
| --- | --- |
| Speeps | Nodallydude |
| Nikkilemondrop | Yorks Crypto |
|  | arte.tez |
|  | Pelago |
|  | 0x_Wes |

**Moderation**

- Roles and Responsibilities (gm Dao and gm Studio)
    1. Channel Upkeep 
        1. Creation, Deletion, Editing, and Archiving. 
    2. Roles
        1. Addition, Removal, Updates.
    3. Content Moderation
        1. Spam and abuse prevention.

| Team Lead(s) | Team Members  |
| --- | --- |
| Ze_Boubs | rich |
| Nodallydude | Sap |
|  | Shneeky |
|  | Willyham |
|  | Cyphr |

### **What is the goal of this proposal?**

- To provide clarity on who in the DAO is responsible for what.
- Unblock people from doing what they need to do!
- Reduce overall workload and dependency on Cyphr, so he can sleep more. Or still sleep less, but at least sleep less doing more things he wants to focus on ;)
- To set up foundational working groups to more easily work towards common goals.
- To provide a framework for the construction of future working groups.
- To reduce “DAO thrash,” by channeling community energy.

### **What is the expected impact of these changes?**

I hope that with these changes engaged community members will have defined spaces to flush out and implement their ideas. I also hope that this makes communication within the DAO easier since we will have a clear delineation of responsibility. Reduce workload on team members who are responsible for multiple things right now. 

### W**hat help might be needed from gmDAO and its members?**

- Discord reorg (Happening now).
- Use of new working groups and process.

### **Sponsors:**