Sumer_Council31_Report_23-11-2021.md 15 KB

Sumer - Council Election Round #33 - Performance Review and Minutes

1 - Basic Information

1.1 - Introduction

The council is expected to produce reports during each round and provide feedback in the form of workflow, challenges, thinking and performance as well as minutes covering important events during the council session.

Usernames referenced are Joystream usernames. All times are calculated based on 6.14 second blocktimes and not actual blocktimes. The Council Round number is taken from the chain, the KPI rounds have an offset number.

1.2 - Council Round Overview

1.3 - Council members & vote participation

  • All usernames are listed in the order given by activeCouncil from chain state.
  • Votes cast includes all types of vote (Approve, Reject, Abstain & Slash)
  • In the event a proposal is not finalized within the current council, it will be indicated and current council votes will not be recorded due to system limitations
Username Member ID Prop. Votes Cast CM Own Stake CM Voter Stake
@ilich 2194 12 15001000 11000000
@lkskrn 644 6 22000000 0
@blackmass 361 7 25000000 0
@joyval 2141 0 26000000 0
@l1dev 515 13 27000000 0
@xfactorus 635 14 19500000 250000
@spat_sochi 1843 4 1000000 21600000
@nanapa6otaet 2531 14 1111 13085000
@nkhlghbl 1962 1 25000000 0
@freakstatic_council 321 10 25000000 0
@kadyrovs 1345 13 15500000 4000000
@tomato 2 10 20000000 5001000
@kalpakci 2137 8 29001000 0
@marinag_mary 1997 9 10000000 13255000
@laura 2329 16 27000000 0
@ururu 790 10 19950000 550000
@sparky 319 0 25000000 0
@igrex 1048 15 21000000 5000000
@zazik 2435 15 25000000 0
@isonar 2182 8 25000000 0
Subtotal: 402953111 73741000
Total: 476694111

1.4 - Council Roles

1.5 - Council Mint & Budget Status

(Note: The council budget is now based on the rewards for roles, council payments and validator payments. Jsgenesis decides how much to set the mint to.)

2 - Minutes

2.1 - Proposal Overview

Proposal Types

  • 25 Proposals Created
    • 9 Text Proposals
    • 7 Spending Proposals
    • 3 SetWorkingGroupLeaderReward Proposals
    • 5 SetWorkingGroupMintCapacity Proposals
    • 0 BeginReviewWorkingGroupLeaderApplication Proposals
    • 0 TerminateWorkingGroupLeaderRole
    • 0 FillWorkingGroupLeaderOpening
    • 1 SetValidatorCount
    • 0 AddWorkingGroupLeaderOpening
    • 0 SetElectionParameters
    • 0 RuntimeUpgrade

Proposal States

  • 15 Approved & executed proposals
  • 1 Canceled proposals
  • 0 Rejected proposals
  • 0 Slashed proposals
  • 0 Expired proposals
  • 9 proposals passed to next council
    • These proposals didn't gather enough quorum in the current council term, so the votes are reset and passed to the next council.

Failed Proposals

  • 0 NotEnoughCapacity failures
  • 0 ExecutionFailed

  • Total time for proposals to finalize: 203.54 hours

  • Average time for proposals to finalize: 13.57 hours

    • This average is calculated from all proposals, including expired proposals but excluding canceled proposals.

2.2 - Proposal Breakdown

Proposal 814 - 31.I-3 - Deputy Council Secretary

Proposal 815 - KPI 31.I-2 - Council Secretary

Proposal 816 - 30.II-3 - Council Term Summary Videos

Proposal 817 - Bounty 18 + 24 report improvements

Proposal 818 - 30.I-4 - Council Minutes

Proposal 819 - OKR Reward for Content Curator

Proposal 820 - Refill operations mint

Proposal 821 - Mint Content Working Group

Proposal 822 - Refill operations mint

Proposal 823 - Reduce validator count 105 > 75

Proposal 824 - Re: joystream-lib & tokenomics refactor

Proposal 825 - Bounty 18. Payments. 13-th week.

Proposal 826 - Quantitative Storage OKRs

Proposal 827 - Weekly Curator Working Group Report 31

Proposal 828 - 31.II-3 - Council Term Summary Videos

Proposal 829 - Refill operations mint

Proposal 830 - Bounty 18 + 24 Static information report

Proposal 831 - Bounty 24. Payments. 8-th week.

Proposal 832 - Bounty 24. Payments. 8-th week.

Proposal 833 - Mint Content Working Group

Proposal 834 - Weekly Storage WG Report 24

Proposal 835 - Update Content Lead Salary

Proposal 836 - Update Storage Lead Salary

Proposal 838 - Curator Lead OKR rewards

Proposal 840 - Update Operations Lead Salary

2.4 - Select threads & events

2.5 - Working Group Spotchecks

3 - Review

3.1 - Workflow, Performance, Challenged & Thinking

4 - Obligations

Council obligations are payments or items that carry through council sessions. These are noted so that future councils can easily see what items they should be aware of. Items can be removed from here once they have been resolved or become outdated.

4.1 Current Documents / Processes

  • Council Report
    • Each council should produce a report which highlights important events, council participation, mint spending and other important facts surrounding the council term
  • Council Budget
    • This is a proposal which tries to guide how many tokens the current council may have available to it during a term. This is a non binding proposal, so is mainly used as a guide for now.

4.2 Regular Payments / Proposals

  • Council Mint
    • The council mint needs to be checked on a regular basis and in the event it is near depletion, a council member should notify a member of Jsgenesis in order for it to be refilled.
    • The council mint is set at a value decided by Jsgenesis.
  • Council Roles
    • Council Secretary
      • This role was introduced in Council Round #18 and the payments are now managed by KPI rewards.
  • Content Curator Mint
    • The Content Curator Mint currently has a maximum value of 5 million tokens.
    • The Content Curator Mint has to be filled periodically and the agreed amount was discussed earlier. The amount may change in the future, but the rewards for this role are dependent on the council passing these proposals in a timely fashion.
    • The Content Curator Lead role is expected to keep track of their mint level and any member of the Joystream platform can create a proposal to refill this mint.
  • Storage Mint
    • The Storage Mint currently has a maximum value of 5 million tokens.
    • This mint has be refilled periodically
    • The Storage Lead role is expected to keep track of their mint level and any member of the Joystream platform can create a proposal to refill this mint.

4.2 Bounties

5 - Report changelog

  • October, November 2021

    • proposals refactor, show amount for spending proposals
  • 04.11.2020

    • added working group review section
  • 22.10.2020

    • updated budget section to reflect nature of new budget system
    • updated events to be threads & events
  • 14.09.2020

    • removed member addresses and replaced with member IDs since they take less space
    • added realized and unrealized spending