# Warcamp Contributor Compensation and Coordinape Notes (3/29/2022)
## Proxy Measurements
- What additional proxy measurements can we put in place to help approximate value levels?
- Weighted Proxy Measurement
- Tracking folks weight over time is also a measurement in itself and gets us closer to an accurate monthly representation of the value of folks contributions
- Current issues with the Coordinape process:
- Potentially biased toward folks who do more *visible* work across the DAO
- Folks all have equally weighted 100 GIVE
## Coordinape Proxy Measurement Process
- Admins can export the Coordinape allocation data (CSV)
- Duplicate the Epoch so that the formulas are preserved
- Paste data in columns B - E
- Eligible:
- Calculating based on who gave
- Giver and non-giver
- Distro
- Amount of HAUS
- 600 HAUS total each month
- This can change if we *decide to*
- Give/HAUS then multipled by the amount of GIVE
- Should add to 600
- This goes into the Disperse Boost
- Import into Google Sheets
-
- Map the ratio of giveHAUS received out of the total to the expected results based on level and value
-
- Move into the Contributors_C3 tab
- There is value to having this each month
- Name, Discord, Address, Month
- Don't calculate the deltas here -- we'd then have multiple Dashboards that would be linked out from here
- Raw table and table with transformations on the source data while doing transformations at the month level
- Preserve the raw data and have the ability to aggregate on top of this
- What degree do we need to do here?
- `importrange` and change to current epoch
- C2:J100
- Eligible -> who is getting paid HAUS
- Received -> what was actually received via Coordinape
- Zero Sum
- Explanations for positive deltas:
- Working more than expected (pure quantity)
- Creating more value on per unit basis than expected
- People *think* you're working more than you are
- People *think* you're providing more value than you are
- Allocate give to those you are directly working with and those whos work impacts you
- And those who directly
- How do we address the Coordinape GIVE fidelity within our current structure?
- Weighting
- Stop sprinkling!
- How do we do this culturally?
- What would help with this argument is to be able to visualize some of the data
- For every month for the past 5 months the folks who are contributing less (time/value wise) are getting overweighted
- Show this, draw conclusion about how this has impact
- Need the data in a better structure
-
## Notes and Questions
- How can we track this data over time?
- What pain points would a *recursive weight* help solve in our Coordinape allocations?
-