Sumer_Council16_Report_10-08-2021.md 21 KB

Sumer - Council Election Round #19 - 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.13 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

  • Council Election Round: #19
  • Council Term: 16
  • Start Block: #1688400
  • End Block: #1789200
  • 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
@lyazufey1812 1905 33 7000000 0
@julysake 2124 13 7500000 0
@blackmass 361 12 7000000 0
@l1dev 515 21 5000000 3500000
@xfactorus 635 27 4000000 1500000
@xandrell 867 30 1000 11200000
@nkhlghbl 1962 4 5000000 0
@doppelganger23 2039 12 5000000 0
@freakstatic_council 321 27 6000000 3010000
@fierydev 439 9 10000000 0
@nexusfallout 4 24 7000000 0
@tomato 2 24 5000000 3341100
@maxlevush 2130 34 1000 6011000
@controlla 2148 19 100000 8600000
@stavr 1027 29 5000000 0
@isonar 2182 21 2000000 3000000
Subtotal: 75602000 40162100
Total: 115764100

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

  • 39 Proposals Created
    • 15 Text Proposals
    • 7 Spending Proposals
    • 3 SetWorkingGroupLeaderReward Proposals
    • 8 SetWorkingGroupMintCapacity Proposals
    • 3 BeginReviewWorkingGroupLeaderApplication Proposals
    • 2 TerminateWorkingGroupLeaderRole
    • 1 FillWorkingGroupLeaderOpening
    • 0 SetValidatorCount
    • 0 AddWorkingGroupLeaderOpening
    • 0 SetElectionParameters
    • 0 RuntimeUpgrade

Proposal States

  • 29 Approved & executed proposals
  • 3 Canceled proposals
  • 1 Rejected proposals
  • 0 Slashed proposals
  • 2 Expired proposals
  • 4 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: 872.33 hours

  • Average time for proposals to finalize: 27.26 hours

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

2.2 - Proposal Breakdown

Proposal 360 - Cut KPI-17 rewards by 35%

Proposal 361 - community-repo: continous updated files

Proposal 362 - Begin Review: Storage

Proposal 363 - Begin Review: Curator

Proposal 364 - Payments to challenge participants

Proposal 365 - Begin Review: Operations

Proposal 366 - Sumer - KPI 16.3 - Council Secretary

Proposal 367 - KPI 16.4 - Deputy Council Secretary

Proposal 368 - Payments to challenge participants

Proposal 369 - Incentive payment (Bounty 16) pt.2

Proposal 370 - Payments to challenge participants

Proposal 371 - Top Burners List

Proposal 372 - Refill operations mint

Proposal 373 - 15.5 - Council Minutes

Proposal 374 - Fill Working Group Mint Capacity

Proposal 375 - Storage WG Mint Refill

Proposal 376 - Weekly Storage WG Report 10

Proposal 377 - Incease Operations budget

Proposal 378 - Change Curator Lead Rewards

Proposal 379 - Change Storage Lead Rewards

Proposal 380 - Change Operations Lead Rewards

Proposal 381 - JSG: please update KPIs.json

Proposal 382 - Payment for Community Bounty #19

Proposal 383 - Fire Content Curator WG Lead

Proposal 384 - test proposal

Proposal 385 - Atlas Thumbnail Preview

Proposal 386 - Storage WG Mint Refill

Proposal 387 - Refill operations mint

Proposal 388 - Fill Curator Group Mint Capacity

Proposal 389 - Refill operations mint

Proposal 390 - Weekly Curator Working Group Report

Proposal 391 - Fire Content Curator WG Lead

Proposal 392 - Refill Operations WG Mint

Proposal 393 - Community Manager role

Proposal 394 - KPI 16.9 - Storage Working Group KPI/OKR

Proposal 395 - OKR Payment for lyazufey1812

Proposal 396 - OKR Payment for mmsaww

Proposal 397 - Council Size=20, Council Term=14days

Proposal 398 - Content Curator WG Leader @Laura

2.4 - Select threads & events

N/A

2.5 - Working Group Spotchecks

  • Storage Role Spot Check: N/A
  • Curator Role Spot Check: N/A
  • Operations Role Spot Check: N/A

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\