Sep 17- 30
We hired an Engagement Lead! Thomas Flitter will start with us on October 4th and will be leading our stakeholder engagement and organizational mapping efforts.
Our Public Call Summary Team is always looking for people. Don’t hesitate to reach out if you’re interested in contributing. And yes, it pays!
Now that we’ve been operating for a couple months we will be updating our budget to reflect more accurate information.
Additionally, our team made an error by confirming the incorrect numbers while setting up our DssVest Dai stream and so we will be using this upcoming budget modification as an opportunity to re-configure our stream.
Since the launch of the CU, we have added a ton to our public drive. Supporting documentation around all our active projects is growing with project plans/descriptions, metrics tracking, and workflow process docs coming into existence and being iteratively improved upon.
We worked with GovAlpha to improve the Governance and Risk call.
The previous format was not scaling with the growing number of Core Units. Team update slots have been replaced by Team Discussion Slots. Core Units should no longer aim to provide a general update, but rather should use this time to present pertinent issues and topics related to their work for the purpose of educating and engaging stakeholders.
Where can you find status updates from the various teams? On the forum of course!
Our team, in partnership with GovAlpha and SES, are working on a plan for scaling MakerDAO meetings to accommodate the increasing number of teams and business initiatives.
Currently we are working on completing resources for two emergency types; Market Events and Wrench Attacks. This is in progress and will be for the coming months as we complete the full set of documentation.
We have started an internal people list, with a public version of this resource planned for the near future. The list contains Facilitators, known team members, known part-time contributors, PPG-OMC-001 members, and Recognised Delegates.
A public version of this list is planned for release in late October.
This has been put on lower priority, with continued progress planned for mid-October as we onboard the recently hired Engagement Lead.
What began as a Team update audit has been expanded to a general “information output” audit. The main difference is that we are not isolating written or presented updates. Instead, we are documenting all the ways teams share information. Soon the DAO will have an easier way of comparing Core Unit information sharing practices, and Core Units will learn what they might be doing that others are not, and vice versa. This project may result in actionable recommendations from our team on how we can all come to closer standards for team updates.
Our team has partnered with Content Production in the creation of an Issue Discussion call series. There is no recurring call schedule for this call series, we will be organizing them as-needed. The next call is currently being planned.
The team has upgraded its training for contributors! Join us and take the relatively short 2-4 hour paid training to start contributing to MakerDAO as a Writer or Quality Assurer.
Maker Relay continues to receive qualitative improvements. Publishing the written version has been handed off from Tim Black to Artem Gordon. Additionally, we are working with Content Production to eventually publish these on an official MakerDAO blog.
We encourage Facilitators, CU members, and senior community members to join the #MakerRelay chat. This way coverage of any given topic can be addressed in a single location where all the collaborators can be found.
The September review is being published this coming Friday!
(Dual effort between MKT-001 & COM-001)
Forum at a Glance
- September Governance Review
- Issue Discussion Call
- 2x sprints planned; Team Information Output Audit & Emergency Playbook
- Public MakerDAO people list
- More progress on everything mentioned above.