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_Council22_Report_21-09-2021.md

Sumer_Council22_Report_21-09-2021.md 14 KB
History Raw

Sumer - Council Election Round #25 - 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.04 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
@kate_fm 1905 20 10,000,000 13,000,000
@ilich 2194 17 9,000,000 15,001,000
@lkskrn 644 5 333,333 14,666,667
@blackmass 361 4 13,000,000 0
@xfactorus 635 14 15,000,000 0
@xandrell 867 13 1,000 22,500,000
@freakstatic_council 321 15 12,000,000 2,000,000
@chiffah 2462 19 1,000 30,361,754
@tomato 2 3 13,941,000 6,500,000
@mmsaww 736 4 13,000,000 0
@kalpakci 2137 16 29,001,000 1,000
@laura 2329 21 20,000,000 10,000,100
@ururu 790 16 11,400,000 1,600,000
@maxlevush 2130 12 500,000 16,500,000
@zazik 2435 17 1,500,000 10,943,457
@kriptos 513 16 4,289,124 20,000,000
Subtotal: 152,966,457 163,073,978
Total: 316,040,435

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

  • 22 Proposals Created
    • 10 Text Proposals
    • 3 Spending Proposals
    • 3 SetWorkingGroupLeaderReward Proposals
    • 6 SetWorkingGroupMintCapacity Proposals
    • 0 BeginReviewWorkingGroupLeaderApplication Proposals
    • 0 TerminateWorkingGroupLeaderRole
    • 0 FillWorkingGroupLeaderOpening
    • 0 SetValidatorCount
    • 0 AddWorkingGroupLeaderOpening
    • 0 SetElectionParameters
    • 0 RuntimeUpgrade

Proposal States

  • 20 Approved & executed proposals
  • 1 Canceled proposals
  • 0 Rejected proposals
  • 0 Slashed proposals
  • 0 Expired proposals
  • 1 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: 178.75 hours

  • Average time for proposals to finalize: 8.94 hours

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

2.2 - Proposal Breakdown

Proposal 571 - KPI 21.5 - Council Minutes

Proposal 572 - Refill Storage WG mint

Proposal 573 - Sumer - KPI 22.3 - Council Secretary

Proposal 574 - Mint Content Working Group

Proposal 575 - 22.4 - Deputy Council Secretary

Proposal 576 - Council Budget #7

Proposal 577 - Refill operations mint

Proposal 578 - Update SP Lead Reward

Proposal 579 - Update Operations Lead Reward

Proposal 580 - Update Curators Lead Reward

Proposal 581 - Task: Opportunities & Applications UI

Proposal 582 - KPI 22.10 - KPIs Overview

Proposal 583 - New BM for Bounty 18

Proposal 584 - New Fiat Pool Scheme

Proposal 585 - Weekly Curator Working Group Report 22

Proposal 586 - Bounty payment 18

Proposal 587 - Refill operations mint

Proposal 588 - Mint Content Working Group

Proposal 589 - OKR Reward for Content Curator

Proposal 590 - Weekly Storage WG Report 15

Proposal 591 - Refill Storage WG mint

Proposal 592 - Payment Curator Lead OKR

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\