🗃️
Contributor Access Bundle DBs
/
Proposed structure for DAOOps

Proposed structure for DAOOps

Proposed By
Essential Intent
Outcome
PASSED
Proposal Date
Nov 16, 2021
Meeting Notes
Type
Structure
Last edited time
Jul 25, 2022
Meeting Notes:
Outcome: Passed ✅
Outcome Summary
This proposal passed, and there will be an async follow-up on the naming in a thread
Proposal
Proposal 2 - Kris
  • Tension: It's difficult for people to understand how we are organized within this new workstream and what should be discussed in which call & which ones to attend.
  • Proposal: Proposed simple structure for DAOOps is as follows
    • DAO Ops Governance Call (aka DOG 🐶 if needed :))
      • = decisions only + status update
      • Limited audience
    • DAO Ops Contributors Call (aka DOC 📃, currently Community Experience call)
      • Inform + coordinate Initiatives within the WS
      • Semi-open call of active contributors (RASCI)
        • Responsible, Accountible, Supporting, Consulted roles only
        • Informed happens during weekly demo call (hosted by Ryan)
      • Initiatives
        • Legal
        • Support
        • Accounting
        • Onboarding
        • People Ops (Values, Mission/Vision, peer feedback process, conflict resolution, …)
        • DAO Tooling (Calendar, Notion, Discord, knowledge DB…)
    • Context
      • Discord already organized in this way
      • Will lead to rename calls for clarity + rename of two channels: DAOOps-governance + DAOOps-Contributors
      • Role '@DAOOps (formerly crossstreamdreamteam) + Gitcoin Core will see everything under DAO Operations.
      • Role '@DAOOps-Governance' can be used to tag people who attend this call
    • Clarifying questions:
      • Growing daoops - own ws - ops call how called? 'dao ops ops'
    • Reactions:
      • Kyle: daoops gov, not like the cross stream call name, prefer that this is cross-stream in the name, names matter
      • Christine: could be either way on the naming
      • Annika: making it clear that it's more than governance of dao operations
      • Fred: make distinction between cross stream
      • Joe: this group empowers what dao ops does
      • Sean: pass
      • Philip: scope clarification, naming is important
      • Simona: title needs clarification, rest all good to me
      • Loie: this is cross stream gov call, would be better to be called something like 'CSG'
      • Scott: most important is being intentional, no further comments
    • Integrated proposal
      • objection: we should rename the WS then
      • contributors is confusing
    • Proposal passed
      • next: Async follow-up on the naming in a thread
🗃️
Contributor Access Bundle DBs
/
Proposed structure for DAOOps

Proposed structure for DAOOps

Proposed By
Essential Intent
Outcome
PASSED
Proposal Date
Nov 16, 2021
Meeting Notes
Type
Structure
Last edited time
Jul 25, 2022
Meeting Notes:
Outcome: Passed ✅
Outcome Summary
This proposal passed, and there will be an async follow-up on the naming in a thread
Proposal
Proposal 2 - Kris
  • Tension: It's difficult for people to understand how we are organized within this new workstream and what should be discussed in which call & which ones to attend.
  • Proposal: Proposed simple structure for DAOOps is as follows
    • DAO Ops Governance Call (aka DOG 🐶 if needed :))
      • = decisions only + status update
      • Limited audience
    • DAO Ops Contributors Call (aka DOC 📃, currently Community Experience call)
      • Inform + coordinate Initiatives within the WS
      • Semi-open call of active contributors (RASCI)
        • Responsible, Accountible, Supporting, Consulted roles only
        • Informed happens during weekly demo call (hosted by Ryan)
      • Initiatives
        • Legal
        • Support
        • Accounting
        • Onboarding
        • People Ops (Values, Mission/Vision, peer feedback process, conflict resolution, …)
        • DAO Tooling (Calendar, Notion, Discord, knowledge DB…)
    • Context
      • Discord already organized in this way
      • Will lead to rename calls for clarity + rename of two channels: DAOOps-governance + DAOOps-Contributors
      • Role '@DAOOps (formerly crossstreamdreamteam) + Gitcoin Core will see everything under DAO Operations.
      • Role '@DAOOps-Governance' can be used to tag people who attend this call
    • Clarifying questions:
      • Growing daoops - own ws - ops call how called? 'dao ops ops'
    • Reactions:
      • Kyle: daoops gov, not like the cross stream call name, prefer that this is cross-stream in the name, names matter
      • Christine: could be either way on the naming
      • Annika: making it clear that it's more than governance of dao operations
      • Fred: make distinction between cross stream
      • Joe: this group empowers what dao ops does
      • Sean: pass
      • Philip: scope clarification, naming is important
      • Simona: title needs clarification, rest all good to me
      • Loie: this is cross stream gov call, would be better to be called something like 'CSG'
      • Scott: most important is being intentional, no further comments
    • Integrated proposal
      • objection: we should rename the WS then
      • contributors is confusing
    • Proposal passed
      • next: Async follow-up on the naming in a thread