<aside> ✏️ Scribes TODOs - DELETE AFTER MEETING

This checklist should be completed by the host(s) and scribe(s) of the meeting

• Before meeting
• During meeting
• After the meeting </aside>

Last meeting

Purpose

A stand-up across D_D Academy sub-teams.

Desired outcomes for the meeting

• The greater Academy team stays up to speed on the big picture.
• Sub-teams highlight blockers and opportunities to collaborate across the initiatives.

Resources

• D_D Academy project page
• D_D Academy Documents
• GitHub Kanban

🎙️ Recording

ADD RECORDING

How to Record a Discord Voice Meeting

🗒️ Agenda & Notes

• Check-in. 30 seconds each: How are you feeling? What are your expectations for the meeting? What are you grateful for?
• 5 minute floor for Team Stewards to highlight events in their domain:
  • Product & Design
  • Pedagogy & Content
  • Development
• 5 minute floor for other updates. Add any other topics for discussion as bullet points below.
  • wolovim - Budget discussion on forum leading up to Q3. Requested one proposal to accomplish simple allocation for S2 + updated request for Q3.
• Check-out. 30 seconds each: How are you feeling? Takeaways from the meeting?

🗣️ Open discussion

• Looking ahead to Q3:
  • uma: for each addition to the platform, track results, e.g., usage traffic
  • D_D can do much more to promote Academy
  • find first beta partner(s)
  • brianfive: highlighting importance of ratifying next iteration of the proposal, given uncertain rewards for so long.
  • kemp: DAO finance tooling in place to support Academy having its own multisig and exist under the Foundation.
  • wolovim: expect a delay or experimental reward for onboarding the first partner(s) as we figure it out.
  • kemp: consider simplifying pay structure where a % just goes to each domain and people are accountable to those domains, instead of managing issue sizing for every ticket, etc.

Untitled