MIP13c3-SP7: Governance Communications
MIP13c3-SP#: 7 Author(s): @twblack88 @DavidUtro Contributors: @JerryAG, @scottrepreneur, @anna, @seth Status: Request for Comments (RFC) Date Proposed: 2020-11-6 Date Ratified: <N/A> Declaration Statement: Maker Governance intends to form a Governance Communications domain with the mandate described in this declaration. Declaration to Replace: n/a
Context and Motivation
MakerDAO needs a system for communication between the DAO, DeFi community, and the public.
Domain teams only have so much time in a day to moderate discussions and keep the project cycle(s) on track. In addition, new users constantly get lost in the deluge of information generated by the community. It’s also clear that as the DAO is moving to formalize operations, and since it will need to communicate with stakeholders and the public, a communications domain team is a possible next step.
Around March 13 2020, a team of contributors came together to start experimenting and explore the contours of this problem space. Thanks to the generosity of community development grants, and project planning, the group produces the Maker Relay, governance call snippets, a governance focused twitter, and coordinates with the governance call summary team. Our intent is to formally confirm that this Domain should exist, outline the mandate of said team, and explore speaking on Governance’s behalf.
Maker Governance declares its intention to form a Governance Communications Domain with the following mandate.
The Governance communications mandate encompasses the facilitation of products, services, and updates that increase the participation and efficiency of MakerDAO’s Governance. This team should condense activity and surface signal for everyone’s benefit.
To facilitate this the Governance Communications Domain will attempt to resolve significant questions/challenges in such a way that provides value to Maker Governance and the other domain teams.
The working group has identified three directions of communication, each of which would be the responsibility of the Governance Communications Domain.
- Communicating information between members of the DAO.
- Communicating from the DAO to the public.
- Communicating from the public to the DAO.
The Governance Communications Domain would operate under the principles of objectivity, simplicity, integrity and brevity.
We believe that these existing initiatives would fall under the Governance Communications Domain’s responsibilities.
- Maker Relay
- A weekly update of governance-related events, including current votes, prior week vote results, proposals, forum deep dive, as well as links to community calls/sync’s, discussions, and useful/relevant information.
- Governance Call Snippets
- An overview of Governance and Risk call, published the same day, ahead of the high-fidelity summary release. It aims to provide domain team updates, important discussions, and links from the chat for anyone unable to make the call or looking for a brief summary.
- Governance Call Summary Team
- An in-depth, high-fidelity summary of the governance call for the more in-depth user that also serves an archival function.
- MKRGov twitter
- A way to update a larger community on governance updates and encourage new users to become active in governance.
- Voices of MakerDAO
- A proposal for creating a podcast/audio version of governance updates.
Domain questions and challenges
- How can a DAO manage Public Relations?
- In what circumstances should we make statements on behalf of the DAO?
- When do we communicate sentiments from the public, from the forums, etc.?
- How can a DAO respond to journalists in a timely and objective manner?
- How can we provide thorough coverage of relevant events/procedures/news?
- How should teams and individuals go about making statements on behalf of the DAO?
- How do we communicate sentiments from the public, from the forums, etc.?
- How can we be as close to objective and unbiased in our communications?
- Can this Domain assist in clarity of working groups and Maker Governance’s actions/intentions?
- How can the DAO become more welcoming to a global audience?
- Create a Domain definition according to the MIP23 template
- Continue producing Maker relay while experimenting with different distribution models and platforms.
- Explore different team structures to share/rotate responsibilities.
- Create a formal framework for the specific tasks and responsibilities team(s) would like to handle.
- Furthermore, surface new useful tasks and responsibilities for Governance and the Community as a whole.
- Validate team utility with data
- Analytics will be collected (depending on where they’re being sourced) and aggregated into specific updates. These will be outlined in one of the frameworks, referred to above.
- Data will assist in quantifying the need for a domain team and responsibilities therein.
- Create documentation, and find a canonical place for it to live.
- This would be written by the Gov-Comms team, and proposed to the general community for comments/questions/clarification.
- Documentation would cover expectations around cadence, execution, role types, products, etc. This may be expanded on later.
- Gov comms Role/responsibilities definition
- Gov comms Roles subproposal: Community Development Roles & Expectations Proposal
- Gov-Comms HackMD workspace, including Relay and Snippets (HackMD)
- Gov-Comms Story (Slide Presentation)
- Gov-Comms Mandate (Doc)
- Canonical Project Planning (Doc)
- DAO Communication Scope / Responsibilities (Doc)
- Github Governance Workflow Ops (Doc)
- Community Driven Gov Messaging (Forum post)
- Reuters: Handbook of Journalism; Freedom From Bias (Relevant Article)
- CDIP 8-Academic Research of MakerDAO
- CDIP 09-Reddit Moderator
- CDIP 30-Voices of MakerDAO