Purpose

The Steward Council has the following objectives:

• Keep track of ongoing Governance Proposals
• Ensure Governance Proposals follow templates and guidelines
• Review, comment and suggest improvements to inflight Governance proposals
• Identify and triage overlaps and conflicts in Governance proposals
• Define the DAO’s Seasonal (Quarterly) strategy, including setting DAO-level OKRs
• Define DAO level budgets (Foundation costs and Treasury assets available for budget requests)

Desired outcomes for the meeting

1. Generate shared context across the DAO
2. Unblock people trying to GTD
3. Improve coordination between different groups

Resources

INSERT SLIDO FOR AGENDA ITEMS

DAO OKRS

🎙️ Recording

How to Record a Discord Voice Meeting

uCJBgNuW2g.m4a

🗒️ Agenda & Notes

• Shout-outs and kudos 🫂
• Governance Proposal Discussion
• Steward Submitted Agenda items

  • Steward vote preparation — added by wolovim

    • Suggested goal: have Stewards in place by start of month 2 (March 1)
    • Action item: assemble calendar, including when announcements need to go out erik
    • Action item: make role as clear as possible with FAQ resources, etc. ASAP kemp
    • Action item: create snapshot weighted voting strategy kemp

  • General “state of the server” update — added by wolovim

    • luan responded to a roadmap request here. summarizing:
      • Feb 28: d_d role planned sunset. when that happens:
        • OG role will be forced to use #select-hub to customize the categories they see.
        • a new d_d role will be assigned to anyone who joined after Jan 31, and they’ll first see a new onboarding flow.
        • wolovim question: is Feb 28 chosen to give time for the onboarding to be completed?
      • MVP for a “support/ticket system” would follow. (wolovim: elaborate?)

  • D_D Labs budget proposal next steps — added by wolovim

    • Suggestion to break into constituent parts as soon as each is ready; partnerships team already executing on deliverables.
    • Proposal Added:

    [DRAFT] DAO Ops

    • Budget breakdowns
      • A Community budget put forward by luan, here. wolovim suggest diving into some category specifics to explain thinking and invite feedback. Round 1: “what do you mean?” Round 2: “what do you like? where might we fall short?”
        • Ad hoc Community-based tasks ($200/mo)
          • Social layers support
        • Community Management ($2000/mo)
          • Minimum 1 weekly call in VC2
          • Proactive engagement
          • Escalating enquiries
          • Research UX enhancements (e.g., bots)
        • Onboarding (x2 roles) ($3000/mo)
          • quest design
          • hosting onboarding sessions
          • re-onboarding program
          • prep and retros
          • research to enhance UX
        • Server Architecture (unpaid)
          • taxonomy design
          • badge design
          • how-to guide
          • support system
        • Community Lead (~$1215/mo)
          • facilitation, support, coordination
        • Safety & Conduct (unpaid)
          • Code of Conduct process, documentation, community/server guidelines
        • Also included: AxisOne ($500/mo), wellness hub ($400/mo), design bounties ($200/mo), tooling (~$85/mo)

  • Getting more data on our community — added by Wikist

  • Using Crew3 for better community engagement — added by Wikist

• (Template for agenda items)
• Open Q&A

🗣️ Open discussion

ADD DISCUSSIONS THAT ARE OUTSIDE THE AGENDA

Untitled