🗃️
Contributor Access Bundle DBs
/
DAO Ops should own the responsibility of communicating results of discussed proposals

DAO Ops should own the responsibility of communicating results of discussed proposals

Proposed By
Essential Intent
Outcome
CHANGES REQUESTED
Proposal Date
Mar 29, 2022
Meeting Notes
Type
Agreement
Last edited time
Jul 28, 2022
Meeting Notes:
Outcome:
Outcome Summary
 
Proposal
CSDO #25
Proposal 1 - Tigress
  • Proposal: DAOops should own the responsibility of communicating results of discussed proposals
    • Posts of passed or failed proposals to be communicated to the governance forum
    • Incubating, tabled, or stalled proposals do not need to be posted as a result of this proposal, though the driver of those proposals could add the conversation if they wish to get community feedback.
    • Alternative 1: DAOops might find the idea of working with a Kanban Board in Notion interesting. However, that would still leave people having to keep track of two sources of information to inform themselves.
    • Alternative 2: Clarify and make explicit who (which role or entitity) should own the responsibility of communicating the outcomes of discussed CSDO proposals. Make explit = write it down as part of an agreement in a “OS Playbook”.
  • Clarifying Questions:
    • Loie: Is the request that Ops Copy-Paste or do a TLDR?
      • Response: Copy-Paste or link; Requesting that we need
    • Kris: What is the need we’re trying to fill? Who is asking for this?
      • Response: This is in effort to increase transperancy and reduce organizational debt
    • Emu: Clarify the question - is this to decide who owns it?
      • Response: CSDO should decide who owns this proposal.
  • Reactions:
    • Loie: Loves this proposal; wants CSDO to be very transparant. This is a step in the direction. Doesn’t think think Ops should own this. The WS who got the proposal passed should own and copy-paste.
    • Kris: Appreciates the desire to bring add’l transparency. People/Stewards are can come to these notes to see decisions made here. Disagrees that DAO Ops should own. Disagrees that this is a priority - We need to get better with communicating what happens here. Hopes we can get to a place where we record CSDO meeting. WSs shouldn’t dictate the responsibilities of another and DAO Ops doesn’t have the bandwidth to take on additional admin tasks
    • Huxwell: We need feedback from the community and some proposal decisions are vaguely notated in CSDO notes; Supports the proposal
    • Emu: Seems like redundant work to cross post; can’t we simply announce these notes are available?
    • Sean: Our bias should be to communicate proposals. DAO Ops should own. To get around bandwidth concerns, DAO Ops should announce that these notes are available. MMM can help provide digestable notes (not copy-paste) posted to Governance Forum.
    • Simona: WS that proposes proposal should be responsible for getting proposal on Gov Forum. We should be aiming for efficient and transparent solution
  • Amendments:
    • Tigress: open to integrating efficient and transparent solution.
    • Will bring revised proposal to next CSDO.
  • Objections?
    • N/A
🗃️
Contributor Access Bundle DBs
/
DAO Ops should own the responsibility of communicating results of discussed proposals

DAO Ops should own the responsibility of communicating results of discussed proposals

Proposed By
Essential Intent
Outcome
CHANGES REQUESTED
Proposal Date
Mar 29, 2022
Meeting Notes
Type
Agreement
Last edited time
Jul 28, 2022
Meeting Notes:
Outcome:
Outcome Summary
 
Proposal
CSDO #25
Proposal 1 - Tigress
  • Proposal: DAOops should own the responsibility of communicating results of discussed proposals
    • Posts of passed or failed proposals to be communicated to the governance forum
    • Incubating, tabled, or stalled proposals do not need to be posted as a result of this proposal, though the driver of those proposals could add the conversation if they wish to get community feedback.
    • Alternative 1: DAOops might find the idea of working with a Kanban Board in Notion interesting. However, that would still leave people having to keep track of two sources of information to inform themselves.
    • Alternative 2: Clarify and make explicit who (which role or entitity) should own the responsibility of communicating the outcomes of discussed CSDO proposals. Make explit = write it down as part of an agreement in a “OS Playbook”.
  • Clarifying Questions:
    • Loie: Is the request that Ops Copy-Paste or do a TLDR?
      • Response: Copy-Paste or link; Requesting that we need
    • Kris: What is the need we’re trying to fill? Who is asking for this?
      • Response: This is in effort to increase transperancy and reduce organizational debt
    • Emu: Clarify the question - is this to decide who owns it?
      • Response: CSDO should decide who owns this proposal.
  • Reactions:
    • Loie: Loves this proposal; wants CSDO to be very transparant. This is a step in the direction. Doesn’t think think Ops should own this. The WS who got the proposal passed should own and copy-paste.
    • Kris: Appreciates the desire to bring add’l transparency. People/Stewards are can come to these notes to see decisions made here. Disagrees that DAO Ops should own. Disagrees that this is a priority - We need to get better with communicating what happens here. Hopes we can get to a place where we record CSDO meeting. WSs shouldn’t dictate the responsibilities of another and DAO Ops doesn’t have the bandwidth to take on additional admin tasks
    • Huxwell: We need feedback from the community and some proposal decisions are vaguely notated in CSDO notes; Supports the proposal
    • Emu: Seems like redundant work to cross post; can’t we simply announce these notes are available?
    • Sean: Our bias should be to communicate proposals. DAO Ops should own. To get around bandwidth concerns, DAO Ops should announce that these notes are available. MMM can help provide digestable notes (not copy-paste) posted to Governance Forum.
    • Simona: WS that proposes proposal should be responsible for getting proposal on Gov Forum. We should be aiming for efficient and transparent solution
  • Amendments:
    • Tigress: open to integrating efficient and transparent solution.
    • Will bring revised proposal to next CSDO.
  • Objections?
    • N/A