Home Explore Help
Register Sign In
Operations
/
community-repo
3
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Tree: 682e0a1d2a
Branches Tags
community-repo
/
council
/
reports
/
sumer-reports
/
Sumer_Council9_Report_23-06-2021.md

Sumer_Council9_Report_23-06-2021.md 14 KB
History Raw

Sumer - Council Election Round #9 - 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 second blocktimes and not actual blocktimes. The Council Round number is taken from the chain, the KPI rounds have an offset number.

This report was compiled by @tomato with assistance from @freakstatic

1.2 - Council Round Overview

  • Council Election Round: #12
  • Council Term: 9
  • Start Block: #982800
  • End Block: #1083600
  • Forum thread for round feedback: N/A

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
@blackmass 361 5 7000000 0
@l1dev 515 0 5000000 4500000
@xfactorus 635 13 401000 4950000
@xandrell 867 15 1000 4200000
@nkhlghbl 1962 10 5000000 4500000
@supunssw 318 0 5000000 0
@freakstatic_council 321 14 5000000 4500000
@leet_joy 957 10 5000000 400000
@fierydev 439 4 11111111 0
@nexusfallout 4 8 7000000 0
@cheomsk 552 12 1000 5710100
@tomato 2 15 5000000 4013100
@kakashi 1323 4 8888 4000000
@maxlevush 2130 15 1000000 6310000
@igrex 1048 14 800000 6015000
@isonar 2182 9 400000 6000000
Subtotal: 57722999 55098200
Total: 112821199

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

  • 17 Proposals Created
    • 10 Text Proposals
    • 3 Spending Proposals
    • 1 SetWorkingGroupLeaderReward Proposals
    • 2 SetWorkingGroupMintCapacity Proposals
    • 1 BeginReviewWorkingGroupLeaderApplication Proposals
    • 0 TerminateWorkingGroupLeaderRole
    • 1 FillWorkingGroupLeaderOpening
    • 0 SetValidatorCount
    • 0 AddWorkingGroupLeaderOpening
    • 0 SetElectionParameters
    • 0 RuntimeUpgrade

Proposal States

  • 14 Approved & executed proposals
  • 1 Canceled proposals
  • 0 Rejected proposals
  • 0 Slashed proposals
  • 0 Expired proposals
  • 2 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

  • 1 NotEnoughCapacity failures

  • 0 ExecutionFailed

  • Total time for proposals to finalize: 166.05 hours

  • Average time for proposals to finalize: 11.07 hours

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

2.2 - Proposal Breakdown

Proposal 164 - Operations Tasks (e)

Proposal 165 - Update curator lead reward

Proposal 166 - Bounty 15 payment

Proposal 167 - Antioch KPI 8.4 - Tokenomics Report

Proposal 168 - Reward for Bounty #10

Proposal 169 - Sumer - KPI 9.2 - Council Secretary

Proposal 170 - Reward for Bounty #10

Proposal 171 - Sumer - KPI 08.4 - Council Minutes

Proposal 172 - Refill the storage mint

Proposal 173 - Operations Tasks (f)

Proposal 174 - Fill Working Group Mint Capacity

Proposal 175 - Changing the Bounty 10 rules

Proposal 176 - Begin review of storage lead apps

Proposal 177 - Storage Group Leader

Proposal 178 - Minimum stake requirements for all roles

Proposal 179 - Sumer KPI 9.x - Budget 5

Proposal 180 - Sumer KPI 9.x - Budget 5 (correction)

Proposal 181 - Operations tasks (g)

2.4 - Select threads & events

N/A

2.5 - Working Group Spotchecks

3 - Review

3.1 - Workflow, Performance, Challenged & Thinking

  • N/A

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

  • 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\