Governance Weekly Meeting
Property
Date
Aug 24, 2022
date
Aug 24, 2022
Tags
Last to edit
- 1- CAKE Scale: - fibo
- https://docs.google.com/spreadsheets/d/1eSJOlKvDz9DlzYjBaxD3Te1tVMmWxyV3jylsFO5dFLc/edit?usp=sharing
- scale on dework,
- task points are CAKE,
- only leads can create tickets
- alert when one person
- 2- coordinape
- 3- CAKE =/ task points - (abstract) - nerd
- assign max cake per working group (5-9),
- CAKE * working group size (proportionally given out to people)
- we normalize distro on a team level rather than org level, ideal team size for any agile team is 5-9, so we assign each workstream a "budget" of points of
5*<#_of_cake _for_featherweight>each season. each team scales task points however they like (no need for consistent scale) bc we'll normalize like how coordinape does to % for distro at end of season. ‣ - ‣‣‣
- ‣‣‣its a signal to allocate human capital to understaffed teams (less people on a team == greater % of team's seasonal one can earn) ‣
- ‣‣‣so we get the % normalization we like from coordinape, with keeping amount of off-chain”
“
so task points in dework =/= cake
% task points in your workstream each season == cakeEarned
Big questions:
- how to determine CAKE?
- the points/values
Next steps:
- flesh out the three proposals (fibo, ispeaknerd)
- get data from dework (fibo)
- follow the forum proposal structure