🗃️
Contributor Access Bundle DBs
/
Adopt a format for CSDO proposals

Adopt a format for CSDO proposals

Proposed By
Essential Intent
Outcome
TABLED
Proposal Date
Mar 8, 2022
Meeting Notes
Type
Agreement
Last edited time
Jul 28, 2022
Meeting Notes:
Outcome: Tabled 🪑
Outcome Summary
 
Proposal
Proposal 3 - Joe
  • Tension: Proposals are broad and unstructured and lead to unfunded decisions or unclear accountability
  • Proposal: Adopt a format for CSDO proposals that includes: (examples below based on proposal to get DAO contributors education opportunities)
    • 1 - An initiative outcome
      • ie. Contributors are able to access $2,000 per year in educational spending. (What is eligible is determined by this initiative)
    • 2 - An initiative driver
      • ie. Jimbob will own this outcome is
    • 3 - An initiative budget
      • Consider launch expense and maintenance costs
      • ie. We will need $500 per week for operations and $30k for the first quarter in reimbursements
        • Operational: $2,000 setup + $500 weekly recurring
        • Expenses: $30,000
        • Total: $38,500
    • 4 - 1 to 3 metrics for success
      • Examples
        • At least x % of this metric
        • 4/6 of these things done
        • Execute on building a that thing
  • Clarifying Questions:
    • Brittney: does it need a budget? Joe: not sure - open to other suggestions
    • Loie: How do we follow with these outcomes? How do we check-in later on to hold people accountable? Joe: Maybe add an expected completion date. Maybe add a section in this meeting for reporting back on previously proposed outcomes
  • Reactions:
    • Kris: Good to define even more, what a good proposal looks like. Our template could be bolstered with clear outcomes. We do have the milestone report, which could serve as a base for this. May not need to pass this, merely follow the infrastructure that exists
    • Owocki: Interesting proposal, maybe we could testdrive this. Governance proposals vs CSDO
    • Brittney: Don’t support this atm because maybe not fleshed out enough. Maybe we don’t need this atm. Not hard requirement.
    • Annika: same hesitation about ‘murkiness’ around this. This may not be necessary for the vast majority of our proposals
    • Loie: I like the proposal. It is a challenge to build outcome awareness. Love having a proposal structure, it seems safe enough to try. Support it philosophically
    • Huxwell: Aligned with annika, but also with the philosophy behind the proposal. Third point could be budget or resources like contributors, et al.
    • Kyle: Supportive. Usually pertains to budget requests. What is missing is some prework and possibly some budgets from CSDO. Supportive for a mix in between.
  • Amendment notes:
    • Suggest to table this for now - we should have hierarchies of problems
  • Objections?
🗃️
Contributor Access Bundle DBs
/
Adopt a format for CSDO proposals

Adopt a format for CSDO proposals

Proposed By
Essential Intent
Outcome
TABLED
Proposal Date
Mar 8, 2022
Meeting Notes
Type
Agreement
Last edited time
Jul 28, 2022
Meeting Notes:
Outcome: Tabled 🪑
Outcome Summary
 
Proposal
Proposal 3 - Joe
  • Tension: Proposals are broad and unstructured and lead to unfunded decisions or unclear accountability
  • Proposal: Adopt a format for CSDO proposals that includes: (examples below based on proposal to get DAO contributors education opportunities)
    • 1 - An initiative outcome
      • ie. Contributors are able to access $2,000 per year in educational spending. (What is eligible is determined by this initiative)
    • 2 - An initiative driver
      • ie. Jimbob will own this outcome is
    • 3 - An initiative budget
      • Consider launch expense and maintenance costs
      • ie. We will need $500 per week for operations and $30k for the first quarter in reimbursements
        • Operational: $2,000 setup + $500 weekly recurring
        • Expenses: $30,000
        • Total: $38,500
    • 4 - 1 to 3 metrics for success
      • Examples
        • At least x % of this metric
        • 4/6 of these things done
        • Execute on building a that thing
  • Clarifying Questions:
    • Brittney: does it need a budget? Joe: not sure - open to other suggestions
    • Loie: How do we follow with these outcomes? How do we check-in later on to hold people accountable? Joe: Maybe add an expected completion date. Maybe add a section in this meeting for reporting back on previously proposed outcomes
  • Reactions:
    • Kris: Good to define even more, what a good proposal looks like. Our template could be bolstered with clear outcomes. We do have the milestone report, which could serve as a base for this. May not need to pass this, merely follow the infrastructure that exists
    • Owocki: Interesting proposal, maybe we could testdrive this. Governance proposals vs CSDO
    • Brittney: Don’t support this atm because maybe not fleshed out enough. Maybe we don’t need this atm. Not hard requirement.
    • Annika: same hesitation about ‘murkiness’ around this. This may not be necessary for the vast majority of our proposals
    • Loie: I like the proposal. It is a challenge to build outcome awareness. Love having a proposal structure, it seems safe enough to try. Support it philosophically
    • Huxwell: Aligned with annika, but also with the philosophy behind the proposal. Third point could be budget or resources like contributors, et al.
    • Kyle: Supportive. Usually pertains to budget requests. What is missing is some prework and possibly some budgets from CSDO. Supportive for a mix in between.
  • Amendment notes:
    • Suggest to table this for now - we should have hierarchies of problems
  • Objections?