community-repo icon indicating copy to clipboard operation
community-repo copied to clipboard

Council Task Performance - WIP

Open mochet opened this issue 4 years ago • 0 comments

Currently Joystream uses a system of KPIs that allow for rewards to be given to council members based on accomplishments during council terms. The current KPI system can be looked at as "good habits" which the council can then work to integrate and improve upon. In a mainnet scenario there may be a KPI system, but the rewards aspect is less clear.

We can define "council tasks" as being the following:

  • Performing spot checks
  • Doing reports
  • Managing Working Groups

Therefore it is maybe important that the council system eventually moves to a transactional one where council members (or whoever does work) submits reports and documents with appropriate spending proposals. For this purpose there is now a rate sheet being worked on: https://github.com/Joystream/community-repo/issues/54 which can be used to guide standardized values for completing tasks.

The benefits of moving to a transactional system for council work are:

  • There is a more direct relationship between tasks + rewards
  • It may become easier to track who is doing tasks
  • The council may become more self-sufficient in completing work
  • Regular Council payments may not need to be so significant (the council salary that is given for just being a council member)
  • Spending Proposals relating to the council would be more consistent, meaning that the amount needed to be minted for work is more predictable.

The negatives of moving to a transactional system for council work are:

  • There may be competition from various parties who want to do work or who have already completed work
  • Spending proposals require using proposals, which may generate too much proposal traffic if there are too many spending proposals

Alongside the rate sheet, it may be useful to have a way to break down each of the reports into a KPI-like system and track the performance of each council in this manner. A document to do this could look something like this:

Council # 1 2 3
Council Report
Tokenomics Report
Storage WG Spot Check 1
Storage WG Spot Check 2
Storage WG Spot Check 3
Curator WG Spot Check 1
Curator WG Spot Check 2
Curator WG Spot Check 3
Score 8/8 6/8 6/8

There could also be an aspect to this of tracking who completes which tasks to help build up a reputation system.

mochet avatar Dec 22 '20 09:12 mochet