Accueil Explorer Aide
S'inscrire Connexion
Operations
/
community-repo
3
0
Fork 0
Fichiers Tickets 0 Pull Requests 0 Wiki
Branche: master
Branches Tags
community-repo
/
council-reports
/
sumer-reports
/
Sumer Council 17 Report - 18-08-2021.md

Sumer Council 17 Report - 18-08-2021.md 17 KB
Lien permanent Historique Raw

Sumer - Council Election Round #20 - 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.05 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: #20
  • Council Term: 17
  • Start Block: #1789200
  • End Block: #1890000
  • 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 26 7500000 2000100
@julysake 2124 8 7500000 0
@blackmass 361 9 7000000 0
@l1dev 515 13 5000000 5100000
@drmarkovi 982 15 4981000 3000000
@xandrell 867 25 1000 14200000
@freakstatic_council 321 19 6000000 3000100
@fierydev 439 13 8888888 0
@nexusfallout 4 15 7000000 0
@tomato 2 13 5000000 4210000
@mmsaww 736 17 4450000 6050000
@laura 2329 24 6700000 11244154
@flakes9776 705 16 7000000 0
@maxlevush 2130 26 1000 7000000
@igrex 1048 26 5000000 3200000
@isonar 2182 8 949000 13000000
Subtotal: 82970888 72004354
Total: 154975242

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

  • 31 Proposals Created
    • 21 Text Proposals
    • 1 Spending Proposals
    • 0 SetWorkingGroupLeaderReward Proposals
    • 9 SetWorkingGroupMintCapacity Proposals
    • 0 BeginReviewWorkingGroupLeaderApplication Proposals
    • 0 TerminateWorkingGroupLeaderRole
    • 0 FillWorkingGroupLeaderOpening
    • 0 SetValidatorCount
    • 0 AddWorkingGroupLeaderOpening
    • 0 SetElectionParameters
    • 0 RuntimeUpgrade

Proposal States

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

  • Average time for proposals to finalize: 12.12 hours

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

2.2 - Proposal Breakdown

Proposal 399 - Refill curation mint

Proposal 400 - 16.5 - Council Minutes

Proposal 401 - Storage WG Mint Refill

Proposal 402 - Storage WG Report 11

Proposal 403 - 17.4 - Deputy Council Secretary

Proposal 404 - Content Curator Lead Report (Statistics)

Proposal 405 - Sumer - KPI 17.3 - Council Secretary

Proposal 406 - Refill operations mint

Proposal 407 - Pending for Bounty 18

Proposal 408 - Review criteria bounty 18

Proposal 409 - Task: Dapplooker Storage Performance

Proposal 410 - Document: Operations - Budget & Workflow

Proposal 411 - Refill operations mint

Proposal 412 - Task: Show salaries on jsstats

Proposal 413 - Storage WG Mint Refill

Proposal 414 - Adding survey results to community-repo

Proposal 415 - Set Working Group Mint Capacity

Proposal 416 - Changes Bounty 18

Proposal 417 - Task: drag-n-drop task list for jsstats

Proposal 418 - Bounty #21: Milestones

Proposal 419 - project "Know your Councils"

Proposal 420 - Refill operations mint

Proposal 421 - Curation Policy

Proposal 422 - Conditions to update Featured Video

Proposal 423 - Task: FAQ and Intro page for jsstats

Proposal 424 - Indicator of effectiveness of curators

Proposal 425 - Refill operations mint

Proposal 426 - Bounty: Create Promotional Content

Proposal 427 - Clean Up Community Repo

Proposal 428 - Storage WG Mint Refill

Proposal 429 - KPI 17-OP1 Runtime Upgrade Testing

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\