Budget Proposal: Probably Nothing newsletter

great stuff @Colin4ward - doing god’s work getting the first budget up and rolling.

pretty much just echo what @RyanCoordinator has said above as well as doing the budget calculation with the hourly to provide a clear budget figure.

one other thing that would be nice to see is a target against the metric/KPIs - “how might we hope to improve against those metrics” i.e:

  • improve open rate by X%
  • improve click-through rate by x%

i’m also not sure what is being suggested here:

-Review period, 2 months, four months?

[DRAFT 2] Rewarding Contributions in $CODE suggests the following which seem like it might be related depending on what @RyanCoordinator means here:

Budgets will be distributed on a monthly basis by the Operations Team.

To help DAO members maintain some visibility of project progress and also to ensure some level of accountability during Season 1, Guilds and Projects must submit a bi-weekly update to the forum to receive the next month’s allocation.

No updates, No $CODE.

If an update is submitted and the Operations Team have any reason to question whether or not the next month’s budget should be issued, they will refer this to the Budget Stewards to Vote on allocating/not-allocating the next month’s budget. This vote will be carried out in public via a sesh bot poll restricted to people who hold the Budget Stewards discord role.

This process will be improved during Season 1 as we figure out better ways of coordinating work and sharing updates across the DAO. Ideally the Budget Stewards is either and elected committee or it is tied to a threshold of $CODE holdings, then delegated power by the DAO to make these decisions on behalf of members.

then would need to submit a new budget for the next season. i’d like to see us evolve the budget stewards to an elected committee who can also handle mid-season requests (this is not fully scoped in the current proposal).

keen for input and ideas here for sure