Setup Payroll

[yeqbfgxjiq]

As described on the website:

• those with longer-term roles -- Curators, Reviewers, and members who maintain the organization's infrastructure -- are best compensated with fixed recurring payments through the Payroll application.
• Payroll is intended to provide a baseline compensation level for consistent contributors.
• Payroll is calculated separately from any compensation earned through tasks or allocations, so it shouldn't be compared to an equivalent salary.
• Members who are added to payroll should have a clearly defined scope of recurring work. A member who has been added to Payroll can choose to claim their allotment in any treasury asset, including Honey.

We first need to determine the HONEY minting/supply schedule.

Then we can determine the % of that payout to be reserved for the Curator, Reviewer, and Allocations Admin for the 1Hive DAO. Open Question: does it make sense to set these as fixed chunks of a pie, or as a base pay for each role?

• if it's a fixed chunk of a pie, as the DAO grows and more Curators/Reviewers are needed to handle the various projects there will be less for each person fulfilling that role. If the value of HONEY goes up as the org scales that would be ok because the real world value would stay the same even if the # of tokens distributed drops. This would also incentivize early contributors, but it might also lead to a "turf war" where current Curators/Reviewers discourage new people from getting involved in these roles due to greed and fear of being diluted. Ultimately BEE/HONEY holders would vote on this, but politics...
• if it's a base pay (say 1000 HONEY or something), then as the org grows that's going to require minting more and more tokens, diluting the current token holders. This could lead to a management bloat where lots of people are managing and collecting tokens, but providing very little real value. This would dilute early contributors due to inflation while potentially providing minimal real value to the DAO.

Based on this quick brainstorm, it seems to be that a fixed chunk of the pie for each role makes the most sense. Happy to change my mind though! :)

[yeqbfgxjiq]

@lkngtn forgot that the Payroll ap was not deployed to Rinkeby yet. My bad. I think it makes sense to wait until Autark ships, then have you deploy it. Once we transition to mainnet we should change all permissions to require a vote, but currently you seem to have a fairly solid understanding of how the CLI works so I think you should keep setting up the DAO (assuming you want to and/or have time).

Also, the latest details on that process can be found in #9

[yeqbfgxjiq]

Any updates on the Payroll app?

[yeqbfgxjiq]

@lkngtn So what's the "long story" with the Payroll app? Is there an ETA or do we have to roll it ourselves?

[lkngtn]

No ETA, if we want to create a payroll process in the near future it may be worthwhile to either explore using something like sablier via agent, start using it without a frontend, or evaluate whether it makes sense to work on the frontend ourselves.