Key Performance Indicators (KPIs) define success metrics for the overall testnet system, and will act as an incentive for the Council to do a good job.

Starting with Antioch, KPI rewards will be distributed to Council Members based on their contributions.

Table of Contents

Overview

For each Council, a new set of KPIs will be released. These will contain a mix of tasks, attempting to target different skills and knowledge.

As soon as the Council is set, the Council Members CMs should try to agree on who is assigned what. If there are any disagreement, Jsgenesis will use the individual "Term Summaries" (see below) and the deliveries to set the individual rewards. This may lead to some "unfair" rulings, but that is unfortunately how it must work.

Finally, as we have tried improving the KPI system, there will surely be some issues along the way. Please bear with us!

Term Summaries

Towards the end of the Term, the Council Secretary will create a forum thread where the CMs can report on their activities.

Within two days (28,800 blocks) of the end of the Term, each CM must report on their KPI activities.
For each KPI they contributed to, write a brief summary of your actions, included an estimate of time spent, and with all related links.

Feel free to include any actions taken not directly related to a KPI.

Grading and Rewards

Within a four days (57,600 blocks) of the end of the Term, the KPIs will be graded.

Note that the reward will only be paid in full if the work done is graded as complete. This will not always be the case. If it turns out the work was far more time consuming than anticipated, the reward may be increased, but this shouldn't be expected.

, the reward wi and the rewards will be minted paid out in tJOY based on the prevailing exchange rate. The fiat pool will be increased proportionally.

Notes

  • x.1 Proposal Clearance is exempt from this
  • If you are participating in the FM program, you should simply link to this post(s), as the same information will be used there.

Current KPIs

Round 4

Annihilation Modes

Although the new KPI scheme is meant to improve the "tragedy of the commons" issue by making them more individual, there are certain things they have to "solve" as a group. If one or more of the items below is not achieved, the Council will not receive ANY KPI rewards, despite otherwise flawless work.

  1. Ensure the 6th Council Election gets >=16 applicants, meaning a new Council is elected on time.

For both the Antioch Council Elections, we have struggled getting a sufficient amount of applicants, leading to the "Announcing Period" being restarted both times (this happens automatically if the number of Applicants is lower than the Council Size).

This is obviously bad, for many reasons, and we want to avoid it happening again.

4.1 - Proposal Clearance

  • Reward: $500
  • Reward Distribution: Shared
  • Grading Process: Automatic
  • Active: Full term
    • Start Block: #478800
    • End Block: #579600

Purpose

For the governance process to function properly, all proposals must be processed effectively, and dealt with within a reasonable time frame. Although we have increased number of proposals that can be open at any time from 5 to 20, it is still important that the community gets a quick result when possible.

This means the Council should be quick to vote when possible, and ask clarifying questions when information is missing.

Scope of Work

For the individual Council Member, this means that they must check in frequently, and address each open proposal. If what is presented is reasonable and within the budget, the proposal should in general be approved.

Of course, the Councils time must be respected, in the sense that the proposal should contain all the information needed to make their verdict. If this is not the case, the proposal discussion system can be used to ask for what is missing.

Without going in too much detail:

  • Most proposals will be of type Text or Spending. Along with some of the Working Group proposals, these should also be the most straight forward to vote on.
  • If the Spending proposal is for a Bounty, make sure the formalities, (eg. ask the Bounty Manager) are in order before casting your vote.
  • If you have all the information you need, vote right away.
    • Regardless of your decision, you should also make a brief comment outlining your reasoning.
  • If you don't have all the information, or don't fully understand, check the comments to see if it has already been addressed. If it hasn't, ask!
  • If you are not sure, you can always:
    • ask in the discussion
      confer with other CMs on Discord and/or the forum
      • if so, this should be linked to or summarized in the discussion
    • vote abstain

Reward Distribution

After the Term is over, we will get all the voting data from the proposals that was open during the Term. The reward will be divided by the number of total proposals.

  • Each time a CM voted for a proposal, they earn 1 point.
  • If they voted the same as the final outcome, they earn 3 more points.
  • If they voted abstain, they also earn 3 more points - as long as they didn't vote abstain on more than 20% of the total proposals.
  • Finally, the first 2 CMs that vote, AND vote "correctly" earns 2 more points.

The CMs reward for each proposal will be proportional to their points.

Note
Once a proposal is finalized, voting stops, so if you want to "piggyback" on the others, you may find yourself not getting to vote in time.

Grading

TBD

4.2 - Council Secretary

  • Reward: $300
  • Reward Distribution: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #478800
    • End Block: 579600#

Purpose

Although this is not a formal role on the platform, having someone responsible for co-ordinating the Council is needed.

The role should be occupied by a "seasoned" Council Member that:

  • is well versed in the platform workings
  • is familiar with github
  • has high availability

Scope of Work

The Council Secretary will act as a bridge between the Council and Jsgenesis. This means:

  • Assigning Jsgenesis to review* all PRs made to the Community Repo, with a link to the spending proposals and other applicable information.
  • Signing off on all reports created
  • Assist and support other CMs
  • Monitor the bounties
    • propose/hire Bounty Managers, set their rewards and secure funding after the fact
    • follow up Bounty Managers (and replace if needed)
    • select the "Weekly Bounty Managers" ref 2.3, according to interest (they will be paid through KPI rewards)
    • ensure the bounty information presented on the website is up to date
    • report on progress after the end of the Term
  • Notify Jsgenesis of urgent and important matters on the testnet
  • Open a forum thread for the "Term Summaries" where the CMs can report on their Council/KPI activities.
  • Ask Jsgenesis to refill the Council Mint in in the #council room on Discord

* Not before all formalities has been completed, eg. approved by the Council

Reward Distribution

Although a single person has the final responsibility, the Council may choose to elect a back-up, deputy, or split the work between bounties and non-bounties.

Grading

TBD

4.3 - Weekly Bounty Managers

  • Reward:
    • Bounty 9: $50 per week
    • Bounty 14: $50 per week
    • Bounty 15: $100 per week
    • Bounty 19: $100 per week
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term + 1 day
    • Start Block: #478800
    • End Block: #594000

Purpose

Keeping track of all bounties is both too much for a single person, and it will require different skillsets. There are currently 4 "weekly" bounties, where "weekly" means that the Bounty Manager isn't meant to have this role until the bounty is completed. Instead, the Council will choose one of their own to act as the Bounty Manager for each bounty during the Term.

Scope of Work

The scope of work for each Bounty will vary quite a lot, depending on the specific bounty.

Some general information can be found here.

Link to Bounties:

After the Council Term has ended, create a brief "handover" report for your successor (even if you are re-elected).

Reward Distribution

Individual. The Council Secretary is responsible for assigning CMs for each Bounty.

Grading

TBD

4.4 - Council Minutes

  • Reward: $200
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term +1 day
    • Start Block: #478800
    • End Block: #594000

Purpose

There needs to be some level of accountability and transparency for the Council. For each Term the Council must produce a report, that both summarizes their communication, covers all 'events' and generally explains what transpired during the Term.

Scope of Work

  1. The 2nd "official" Council on Babylon (#118800-#219600) produces a report covering any and all "events" of interest:
  • Proposals
  • Decisions
  • Voting statistics
  • etc.
  1. The Council Produces a "Tokenomics" report covering the quantitative aspects of the Term. Must include:
  • Issuance statistics, through:
    • Spending from proposals
    • Role rewards
    • Bounties paid
    • Validator rewards
    • Total tokens minted
    • Total tokens burned
  • Media statistics
  • Membership statistics
  • Role occupants, their recurring and earned rewards, hired dates, etc.
  • Forum statistics

Previous Council reports can be used as a guideline.

Reward Distribution

If multiple reports are proposed, only the best one will be rewarded.
Ideally however, this would be a collaborative effort.

Grading

TBD

4.5 Find All PRs/Issues That Require Jsgenesis Action

  • Reward: $100
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Final day (14400 blocks)
    • Start Block: #565200
    • End Block: #579600

Purpose

As we are often behind on certain issues, and have multiple github repos (and discord) to monitor, assistance is often needed.

We need to compile a list of actions required.

Scope of Work

Towards the end of the term, go through the following repos, and look for open issues and PRs made by someone outside of the "organization", that has not been solved/addressed:

  • joystream
  • helpdesk
  • hydra
  • community-repo
  • atlas
  • founding-members
  • joystream-org
  • handbook

Then, go through the Discord channels (last week only), and add questions/comments that needs to be addressed.

Finally, create an issue in the community repo with a brief TL;DR for each, and a link to the issue/pr.

Note that this issue may be of help, but ensure the items are still not addressed before you make the new issue!

Reward Distribution

If multiple issues are created, only the best one will be rewarded.

Grading

TBD

4.6 Discord Channel Management

  • Reward: $50 Per Channel Group
    1. Testnet Roles
    • #validator
    • #storage-provider
    • #content-curator
    • #content-creator
    • #tech-support
    1. Governance
    • #council
    • #proposal
    • #bounties
    1. Newcomers
    • #general
    • #welcome
    • #introduce-yourself
    • #faucet
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term + 1 day
    • Start Block: #478800
    • End Block: #594000

Purpose

To make the Joystream community more welcoming to newcomers on Discord, we need high availability and helpfulness there.

Scope of Work

For each of the above groups (1-3):
Check in multiple times every day, and welcome/assist every user that posts or asks a question. You need to have some knowledge of the particular topic, or read up on it. If you still don't know the answer, tag someone else!

Reward Distribution

Also note that you will "keep" this role for 1 day (14,400 blocks) AFTER the term to allow a new CM to take over.

Grading is individual.

Grading

TBD

4.7 Manage the Storage Working Group

  • Reward: $200
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #478800
    • End Block: #579600

Purpose

As the Storage lead is not yet hired, this is a critical task that needs focus.

Scope of Work

In no particular order:

  1. Ensure a new Lead is hired (with stake and rewards).
  2. Create a budget, that calculates the rewards for both the Lead and n workers. This budget must consider:
  • Time spent on hiring, management, performance (spot) checks (Lead only)
  • Actual running costs
  • Set budgets assuming the Lead will hire 5 workers during the Term
  1. Formalize the reporting requirements for the Lead. See helpdesk for details.
  2. Follow up the Lead, and ensure they are performing their work, completes hiring of at least 3 workers (with stake and rewards), and ensures they deploy their storage nodes.
  3. Ensure the Lead adjusts the workers rewards weekly (as the rate changes)
  4. Sign off on the Leads reports.

Reward Distribution

Grading is individual. If the proposals created in relation to the tasks above are made by different CMs, the rewards will be shared based on the assumed workloads.

Grading

TBD

4.8 Manage the Content Curators Working Group

  • Reward: $200
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #478800
    • End Block: #579600

Purpose

Although the working groups Leads are expected to run the day to day, they must be monitored by the Council.

With this KPI, they will also take on a bigger workload.

Scope of Work

In no particular order:

  1. Approve/update the previous budget, that calculated the rewards for both the Lead and n workers. This budget must consider:
  • Time spent on hiring, management, performance (spot) checks (Lead only)
  • Time spent on performing their Curation duties
  • Set budgets assuming there will be a total of 10 Curators at the end of the Term
  1. Formalize/update the reporting requirements for the Lead. See helpdesk for details.
  2. Follow up the Lead, and ensure they are performing their work
  • ensure they have configured curation groups with "appropriate" permissions
  • their reporting duties are maintained
  • a curator is chosen, and performing their duties as, the BM for Bounty #10
  • a curator is chosen, and performing their duties as, the BM for Bounty #18
  1. Ensure the Lead adjusts the workers rewards weekly (as the rate changes)
  2. Sign off on the Leads reports.

Reward Distribution

Grading is individual. If the proposals created in relation to the tasks above are made by different CMs, the rewards will be shared based on the assumed workloads.

4.9 Proposal Creation

  • Reward: $300
  • Reward Distribution: Shared
  • Grading Process: Automatic
  • Active: Full term
    • Start Block: #478800
    • End Block: #579600

Purpose

Although somewhat related to all the individual KPIs, there seems to be some hesitation to actually creating the proposals. Lets reward it!

Scope of Work

This KPI rewards the creator of each proposal that:

  1. Is made by a CM
  2. Gets approved

Reward Distribution

Let:

  • P_c be the number of proposals that gets created by a CM during the term
  • P_a be the number proposals that gets approved during the term
  • P_na be the number proposals is finalized, but not approved, during the term
  • R is the reward
  • *,n is the * for a CM

For each CM:

R,n = R * (P_a,n-P_na,n)/P_c

Grading

TBD

4.10 Council Explainer Video (Continued)

  • Reward: $300
  • Reward Distribution: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #478800
    • End Block: #579600

Purpose

Explainer videos is something we want to have for many different aspects of the platform.

Who is more qualified to make/design one for the Council, than the Council?

Scope of Work

Start by sourcing all the information required to explain the Council for one, or both of these two groups:

  1. Someone that doesn't know anything about the Council
  2. Someone that is trying to get elected or newly elected

Then, make a script and sketches for what these videos should say. Your work will likely be made in to a bounty.

Reward Distribution

If multiple proposals are made, the reward will be split by how much of each is used when the Bounty is created.

Note that the rewards listed ($300) is the total - eg. the sum of 2.11+3.11.

Grading

TBD

4.11 - Create a "State of Joystream" Report (continued)

  • Reward: $250
  • Reward Distribution: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #378000
    • End Block: #478800

Purpose

To better illustrate to new users how Joystream as a platform has evolved over time, a regular report would be a good way of collecting together some of the data already on the platform.

Scope of Work

  • Leaving aside the platform and technical issues/improvements, how has user growth been over the past 3 months. Use tokenomics reports, council reports and other data to show how the project is growing and evolving.
    • Number of accounts with tokens
    • Number of transactions/extrinsics pr week
      • Number of transactions/extrinsics pr module pr week
    • Memberships
      • Forum posts
      • Content directory growth
        • Some data may be inaccessible due to the chain crash unfortunately

In order to get a full picture, this report will need to track data from the "previous" chain.
This data can be accessed using previous versions of the joystream types, and connecting to wss://babylon.joystreamstats.live:9945.

Note that whatever happened AFTER #2,528,244 should be discarded.

Reward Distribution

If multiple reports are proposed, only the best one will be rewarded.

Grading

TBD

4.12 - Get Historical Exchange Rate

  • Reward: $200
  • Reward Distribution: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #378000
    • End Block: #478800

Purpose

In order to get a better overview of how the token price has fluctuated in value, we need an overview of the in- and outflows of fiat, and the issuance change.

Scope of Work

Create a script (or mulitple) that fetches:

  1. All the fiat pool increases, and cashouts from the status-server

The status server currently includes data both from the current and the previous (defunct) chain. Keep in mind that you need to separate which blocks refer to the "old" and "new" chain. As all exchanges/burns/dollarPoolChanges was added chronologically, this shouldn't be a problem.

  1. The current totalIssuance every 600th block.

Again, the script(s) needs to fetch the issuance data from wss://babylon.joystreamstats.live:9945 (up to block 2594784) and the new chain.

Publish both scripts, and a json that, for every 600th block includes:

  • blockHeight
  • time
  • issuance
  • fiatPool
  • rate

Reward Distribution

If multiple reports are proposed, only the best one will be rewarded.

Grading

TBD

Previous KPIs

Round 3

  • KPIs: 12
  • Total Possible Rewards: $3400
  • Council Elected in Round: 5
  • Council Members: 16
  • Term Length: 7 days / 100800 blocks
    • Start Block/Date: #277200 / 04.05.21
    • End Block/Date: #478800 / 11.05.21
  • Term Summaries Forum Thread: TBD
  • Deadline to Submit Summary: #507600

Annihilation Modes

Although the new KPI scheme is meant to improve the "tragedy of the commons" issue by making them more individual, there are certain things they have to "solve" as a group. If one or more of the items below is not achieved, the Council will not receive ANY KPI rewards, despite otherwise flawless work.

  1. Ensure the 6th Council Election gets >=16 applicants, meaning a new Council is elected on time.

For both the Antioch Council Elections, we have struggled getting a sufficient amount of applicants, leading to the "Announcing Period" being restarted both times (this happens automatically if the number of Applicants is lower than the Council Size).

This is obviously bad, for many reasons, and we want to avoid it happening again.

3.1 - Proposal Clearance

  • Reward: $500
  • Reward Distribution: Shared
  • Grading Process: Automatic
  • Active: Full term
    • Start Block: #378000
    • End Block: #478800

Purpose

For the governance process to function properly, all proposals must be processed effectively, and dealt with within a reasonable time frame. Although we have increased number of proposals that can be open at any time from 5 to 20, it is still important that the community gets a quick result when possible.

This means the Council should be quick to vote when possible, and ask clarifying questions when information is missing.

Scope of Work

For the individual Council Member, this means that they must check in frequently, and address each open proposal. If what is presented is reasonable and within the budget, the proposal should in general be approved.

Of course, the Councils time must be respected, in the sense that the proposal should contain all the information needed to make their verdict. If this is not the case, the proposal discussion system can be used to ask for what is missing.

Without going in too much detail:

  • Most proposals will be of type Text or Spending. Along with some of the Working Group proposals, these should also be the most straight forward to vote on.
  • If the Spending proposal is for a Bounty, make sure the formalities, (eg. ask the Bounty Manager) are in order before casting your vote.
  • If you have all the information you need, vote right away.
    • Regardless of your decision, you should also make a brief comment outlining your reasoning.
  • If you don't have all the information, or don't fully understand, check the comments to see if it has already been addressed. If it hasn't, ask!
  • If you are not sure, you can always:
    • ask in the discussion
      confer with other CMs on Discord and/or the forum
      • if so, this should be linked to or summarized in the discussion
    • vote abstain

Reward Distribution

After the Term is over, we will get all the voting data from the proposals that was open during the Term. The reward will be divided by the number of total proposals.

  • Each time a CM voted for a proposal, they earn 1 point.
  • If they voted the same as the final outcome, they earn 3 more points.
  • If they voted abstain, they also earn 3 more points - as long as they didn't vote abstain on more than 20% of the total proposals.
  • Finally, the first 2 CMs that vote, AND vote "correctly" earns 2 more points.

The CMs reward for each proposal will be proportional to their points.

Note
Once a proposal is finalized, voting stops, so if you want to "piggyback" on the others, you may find yourself not getting to vote in time.

Grading

TBD

3.2 - Council Secretary

  • Reward: $300
  • Reward Distribution: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #378000
    • End Block: #478800

Purpose

Although this is not a formal role on the platform, having someone responsible for co-ordinating the Council is needed.

The role should be occupied by a "seasoned" Council Member that:

  • is well versed in the platform workings
  • is familiar with github
  • has high availability

Scope of Work

The Council Secretary will act as a bridge between the Council and Jsgenesis. This means:

  • Assigning Jsgenesis to review* all PRs made to the Community Repo, with a link to the spending proposals and other applicable information.
  • Signing off on all reports created
  • Assist and support other CMs
  • Monitor the bounties
    • propose/hire Bounty Managers, set their rewards and secure funding after the fact
    • follow up Bounty Managers (and replace if needed)
    • select the "Weekly Bounty Managers" ref 2.3, according to interest (they will be paid through KPI rewards)
    • ensure the bounty information presented on the website is up to date
    • report on progress after the end of the Term
  • Notify Jsgenesis of urgent and important matters on the testnet
  • Open a forum thread for the "Term Summaries" where the CMs can report on their Council/KPI activities.
  • Ask Jsgenesis to refill the Council Mint in in the #council room on Discord

* Not before all formalities has been completed, eg. approved by the Council

Reward Distribution

Although a single person has the final responsibility, the Council may choose to elect a back-up, deputy, or split the work between bounties and non-bounties.

Grading

TBD

3.3 - Weekly Bounty Managers

  • Reward:
    • Bounty 9: $50 per week
    • Bounty 14: $50 per week
    • Bounty 15: $100 per week
    • Bounty 19: $100 per week
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term + 1 day
    • Start Block: #378000
    • End Block: #478800

Purpose

Keeping track of all bounties is both too much for a single person, and it will require different skillsets. There are currently 4 "weekly" bounties, where "weekly" means that the Bounty Manager isn't meant to have this role until the bounty is completed. Instead, the Council will choose one of their own to act as the Bounty Manager for each bounty during the Term.

Scope of Work

The scope of work for each Bounty will vary quite a lot, depending on the specific bounty.

Some general information can be found here.

Link to Bounties:

After the Council Term has ended, create a brief "handover" report for your successor (even if you are re-elected).

Reward Distribution

Individual. The Council Secretary is responsible for assigning CMs for each Bounty.

Grading

TBD

3.4 - Council Surveys Continued

  • Reward: $300
  • Reward Distribution: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #378000
    • End Block: #478800

Purpose

With a new KPI scheme, we need to find out what the issues were, and, if possible, how to address them.

As can be seen from the Annihilation, we also need to know what can be done to increase the "interest" in becoming a Council Member

This is obviously bad, for many reasons, and we want to avoid it happening again.

Scope of Work

Create three surveys, to the groups outlined below:

  1. The previous Council (term ended #277200)
  2. The current Council (term ends #378000)
  3. Members that Announced their candidacy, but weren't elected
  4. "Everyone" else

Define and ask some specific questions, that answer the more high level topics we need information for (target groups):

  • What did you think about the KPIs (1,2)
  • Did the Council co-operate well (1,2)
  • What do you expect your implied "hourly wage" to be after the term (1,2)
  • What made you apply to the Council (1-3)
  • What did you expect "hourly wage" to be before applying (1-3)
  • What did you do get elected (1-3)
  • Did you expect to get elected (1-3)
  • When did you first learn about the Council (1-4)
  • Why did you not apply to the Council (1-4)

The results must be presented in a comprehensive way, with notes to account for possible irregularities, unclear questions/answers, etc.

Notes

  • Simply questions above will not be sufficient to get a full score.
    • You are excepted to break them in to (mostly) multiple choice questions
    • Spend some time thinking about from Jsgenesis POV, and see if you can use the survey to help us create better KPIs, and possibly workflows, through additional questions
  • We will pay 5000tJOY to all members (that was a member before block #219600) answering one or more survey, so make sure they leave their address

Reward Distribution

If multiple surveys are delivered, only the best one will be rewarded. Having said that, co-operation would likely make for a significantly better survey.

Note that the rewards listed ($300) is the total - eg. the sum of 2.4+3.4.

Grading

TBD

3.5 - Council Minutes

  • Reward: $200
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #378000
    • End Block: #478800

Purpose

There needs to be some level of accountability and transparency for the Council. For each Term the Council must produce a report, that both summarizes their communication, covers all 'events' and generally explains what transpired during the Term.

Scope of Work

  1. The 3rd "official" Council on Babylon (#378000-#478800) produces a report covering any and all "events" of interest:
  • Proposals
  • Decisions
  • Voting statistics
  • etc.
  1. The Council Produces a "Tokenomics" report covering the quantitative aspects of the Term. Must include:
  • Issuance statistics, through:
    • Spending from proposals
    • Role rewards
    • Bounties paid
    • Validator rewards
    • Total tokens minted
    • Total tokens burned
  • Media statistics
  • Membership statistics
  • Role occupants, their recurring and earned rewards, hired dates, etc.
  • Forum statistics

Previous Council reports can be used as a guideline.

Reward Distribution

If multiple reports are proposed, only the best one will be rewarded.
Ideally however, this would be a collaborative effort.

Grading

TBD

3.6 - Find All PRs/Issues That Require Jsgenesis Action

  • Reward: $100
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Final day (14400 blocks)
    • Start Block: #378000
    • End Block: #478800

Purpose

As we are often behind on certain issues, and have multiple github repos (and discord) to monitor, assistance is often needed.

We need to compile a list of actions required.

Scope of Work

Towards the end of the term, go through the following repos, and look for open issues and PRs made by someone outside of the "organization", that has not been solved/addressed:

  • joystream
  • helpdesk
  • hydra
  • community-repo
  • atlas
  • founding-members
  • joystream-org
  • handbook

Then, go through the Discord channels (last week only), and add questions/comments that needs to be addressed.

Finally, create an issue in the community repo with a brief TL;DR for each, and a link to the issue/pr.

Note that this issue may be of help, but ensure the items are still not addressed before you make the new issue!

Reward Distribution

If multiple issues are created, only the best one will be rewarded.

Grading

TBD

3.7 - Discord Channel Management

  • Reward: $50 Per Channel Group
    1. Testnet Roles
    • #validator
    • #storage-provider
    • #content-curator
    • #content-creator
    • #tech-support
    1. Governance
    • #council
    • #proposal
    • #bounties
    1. Newcomers
    • #general
    • #welcome
    • #introduce-yourself
    • #faucet
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term + 1 day
    • Start Block: #378000
    • End Block: #478800

Purpose

To make the Joystream community more welcoming to newcomers on Discord, we need high availability and helpfulness there.

Scope of Work

For each of the above groups (1-3):
Check in multiple times every day, and welcome/assist every user that posts or asks a question. You need to have some knowledge of the particular topic, or read up on it. If you still don't know the answer, tag someone else!

Reward Distribution

Also note that you will "keep" this role for 1 day (14,400 blocks) AFTER the term to allow a new CM to take over.

Grading is individual.

Grading

TBD

3.8 - Manage the Storage Working Group

  • Reward: $200
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #378000
    • End Block: #478800

Purpose

Only the lead has been hired, so more workers and follow up is needed!

Scope of Work

In no particular order:

  1. Ensure a new Lead is hired (with stake and rewards).
  2. Create a budget, that calculates the rewards for both the Lead and n workers. This budget must consider:
  • Time spent on hiring, management, performance (spot) checks (Lead only)
  • Actual running costs
  • Set budgets assuming the Lead will hire 5 workers during the Term
  1. Formalize the reporting requirements for the Lead. See helpdesk for details.
  2. Follow up the Lead, and ensure they are performing their work, completes hiring of at least 3 workers (with stake and rewards), and ensures they deploy their storage nodes.
  3. Ensure the Lead adjusts the workers rewards weekly (as the rate changes)
  4. Sign off on the Leads reports.

Reward Distribution

Grading is individual. If the proposals created in relation to the tasks above are made by different CMs, the rewards will be shared based on the assumed workloads.

Grading

TBD

3.9 - Manage the Content Curators Working Group

  • Reward: $200
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #378000
    • End Block: #478800

Purpose

Although the working groups Leads are expected to run the day to day, they must be monitored by the Council.

With this KPI, they will also take on a bigger workload.

Scope of Work

In no particular order:

  1. Approve/update the previous budget, that calculated the rewards for both the Lead and n workers. This budget must consider:
  • Time spent on hiring, management, performance (spot) checks (Lead only)
  • Time spent on performing their Curation duties
  • Set budgets assuming there will be a total of 10 Curators at the end of the Term
  1. Formalize/update the reporting requirements for the Lead. See helpdesk for details.
  2. Follow up the Lead, and ensure they are performing their work
  • ensure they have configured curation groups with "appropriate" permissions
  • their reporting duties are maintained
  • a curator is chosen, and performing their duties as, the BM for Bounty #10
  • a curator is chosen, and performing their duties as, the BM for Bounty #18
  1. Ensure the Lead adjusts the workers rewards weekly (as the rate changes)
  2. Sign off on the Leads reports.

Reward Distribution

Grading is individual. If the proposals created in relation to the tasks above are made by different CMs, the rewards will be shared based on the assumed workloads.

3.10 - Proposal Creation

  • Reward: $300
  • Reward Distribution: Shared
  • Grading Process: Automatic
  • Active: Full term
    • Start Block: #378000
    • End Block: #478800

Purpose

Although somewhat related to all the individual KPIs, there seems to be some hesitation to actually creating the proposals. Lets reward it!

Scope of Work

This KPI rewards the creator of each proposal that:

  1. Is made by a CM
  2. Gets approved

Reward Distribution

Let:

  • P_c be the number of proposals that gets created by a CM during the term
  • P_a be the number proposals that gets approved during the term
  • P_na be the number proposals is finalized, but not approved, during the term
  • R is the reward
  • *,n is the * for a CM

For each CM:

R,n = R * (P_a,n-P_na,n)/P_c

Grading

TBD

3.11 - Council Explainer Video (Continued)

  • Reward: $300
  • Reward Distribution: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #378000
    • End Block: #478800

Purpose

Explainer videos is something we want to have for many different aspects of the platform.

Who is more qualified to make/design one for the Council, than the Council?

Scope of Work

Start by sourcing all the information required to explain the Council for one, or both of these two groups:

  1. Someone that doesn't know anything about the Council
  2. Someone that is trying to get elected or newly elected

Then, make a script and sketches for what these videos should say. Your work will likely be made in to a bounty.

Reward Distribution

If multiple proposals are made, the reward will be split by how much of each is used when the Bounty is created.

Note that the rewards listed ($300) is the total - eg. the sum of 2.11+3.11.

Grading

TBD

3.12 - Create a "State of Joystream" Report

  • Reward: $250
  • Reward Distribution: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #378000
    • End Block: #478800

Purpose

To better illustrate to new users how Joystream as a platform has evolved over time, a regular report would be a good way of collecting together some of the data already on the platform.

Scope of Work

  • Leaving aside the platform and technical issues/improvements, how has user growth been over the past 3 months. Use tokenomics reports, council reports and other data to show how the project is growing and evolving.
    • Number of accounts with tokens
    • Number of transactions/extrinsics pr week
      • Number of transactions/extrinsics pr module pr week
    • Memberships
      • Forum posts
      • Content directory growth
        • Some data may be inaccessible due to the chain crash unfortunately

In order to get a full picture, this report will need to track data from the "previous" chain.
This data can be accessed using previous versions of the joystream types, and connecting to wss://babylon.joystreamstats.live:9945.

Note that whatever happened AFTER #2,528,244 should be discarded.

Reward Distribution

If multiple reports are proposed, only the best one will be rewarded.

Grading

TBD

Round 2

KPI #2

  • KPIs: 11
  • Total Possible Rewards: $2750
  • Council Elected in Round: 2
  • Council Members: 16
  • Term Length: 7 days / 100800 blocks
    • Start Block/Date: #277200 / 26.04.21
    • End Block/Date: #378000 / 04.05.21
  • Term Summaries Forum Thread: TBD
  • Deadline to Submit Summary: #406800

Results

Member ID Member Handle Reward [USD] Reward [tJOY]
361 blackmass 11 294183
515 l1dev 5 133719
635 xfactorus 99 2647645
129 anthony 23 615109
867 xandrell 103 2754621
1962 nkhlghbl 100 2674389
2039 doppelganger23 51 1363938
321 freakstatic_council 192 5134827
957 leet_joy 45 1203475
439 fierydev 26 695341
552 cheomsk 29 775573
2 tomato 679 18159101
525 oiclid 262 7006899
319 sparky 0 0
1369 lopegor 138 3690657
355 manipal 0 0
SUM 16 1763 47149477

Paid out on block 457317.

Annihilation Modes

Although the new KPI scheme is meant to improve the "tragedy of the commons" issue by making them more individual, there are certain things they have to "solve" as a group. If one or more of the items below is not achieved, the Council will not receive ANY KPI rewards, despite otherwise flawless work.

  1. Ensure the 4th Council Election gets >=16 applicants, meaning a new Council is elected on time.

For both the Antioch Council Elections, we have struggled getting a sufficient amount of applicants, leading to the "Announcing Period" being restarted both times (this happens automatically if the number of Applicants is lower than the Council Size).

This is obviously bad, for many reasons, and we want to avoid it happening again.

2.1 Proposal Clearance

  • Reward: $500
  • Reward Distribution: Shared
  • Grading Process: Automatic
  • Active: Full term
    • Start Block: #277200
    • End Block: #378000

Purpose

For the governance process to function properly, all proposals must be processed effectively, and dealt with within a reasonable time frame. Although we have increased number of proposals that can be open at any time from 5 to 20, it is still important that the community gets a quick result when possible.

This means the Council should be quick to vote when possible, and ask clarifying questions when information is missing.

Scope of Work

For the individual Council Member, this means that they must check in frequently, and address each open proposal. If what is presented is reasonable and within the budget, the proposal should in general be approved.

Of course, the Councils time must be respected, in the sense that the proposal should contain all the information needed to make their verdict. If this is not the case, the proposal discussion system can be used to ask for what is missing.

Without going in too much detail:

  • Most proposals will be of type Text or Spending. Along with some of the Working Group proposals, these should also be the most straight forward to vote on.
  • If the Spending proposal is for a Bounty, make sure the formalities, (eg. ask the Bounty Manager) are in order before casting your vote.
  • If you have all the information you need, vote right away.
    • Regardless of your decision, you should also make a brief comment outlining your reasoning.
  • If you don't have all the information, or don't fully understand, check the comments to see if it has already been addressed. If it hasn't, ask!
  • If you are not sure, you can always:
    • ask in the discussion
      confer with other CMs on Discord and/or the forum
      • if so, this should be linked to or summarized in the discussion
    • vote abstain

Reward Distribution

After the Term is over, we will get all the voting data from the proposals that was open during the Term. The reward will be divided by the number of total proposals.

  • Each time a CM voted for a proposal, they earn 1 point.
  • If they voted the same as the final outcome, they earn 3 more points.
  • If they voted abstain, they also earn 3 more points - as long as they didn't vote abstain on more than 20% of the total proposals.
  • Finally, the first 2 CMs that vote, AND vote "correctly" earns 2 more points.

The CMs reward for each proposal will be proportional to their points.

Note
Once a proposal is finalized, voting stops, so if you want to "piggyback" on the others, you may find yourself not getting to vote in time.

Grading

Member ID Member Handle Voted Points Reward
361 blackmass 3 12 11
515 l1dev 2 5 5
635 xfactorus 14 52 49
129 anthony 7 25 23
867 xandrell 13 46 43
1962 nkhlghbl 14 53 50
2039 doppelganger23 14 54 51
321 freakstatic_council 14 58 54
957 leet_joy 13 48 45
439 fierydev 7 28 26
552 cheomsk 8 31 29
2 tomato 11 42 39
525 oiclid 9 39 37
319 sparky 0 0 0
1369 lopegor 11 41 38
355 manipal 0 0 0
SUM 16 140 534 500

2.2 - Council Secretary

  • Reward: $300
  • Reward Distribution: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #277200
    • End Block: #378000

Purpose

Although this is not a formal role on the platform, having someone responsible for co-ordinating the Council is needed.

The role should be occupied by a "seasoned" Council Member that:

  • is well versed in the platform workings
  • is familiar with github
  • has high availability

Scope of Work

The Council Secretary will act as a bridge between the Council and Jsgenesis. This means:

  • Assigning Jsgenesis to review* all PRs made to the Community Repo, with a link to the spending proposals and other applicable information.
  • Signing off on all reports created
  • Assist and support other CMs
  • Monitor the bounties
    • propose/hire Bounty Managers, set their rewards and secure funding after the fact
    • follow up Bounty Managers (and replace if needed)
    • select the "Weekly Bounty Managers" ref 2.3, according to interest (they will be paid through KPI rewards)
    • ensure the bounty information presented on the website is up to date
    • report on progress after the end of the Term
  • Notify Jsgenesis of urgent and important matters on the testnet
  • Open a forum thread for the "Term Summaries" where the CMs can report on their Council/KPI activities.
  • Ask Jsgenesis to refill the Council Mint in in the #council room on Discord

* Not before all formalities has been completed, eg. approved by the Council

Reward Distribution

Although a single person has the final responsibility, the Council may choose to elect a back-up, deputy, or split the work between bounties and non-bounties.

Grading

  • @tomato - $250/$300
    • Assigning Jsgenesis community repo review - tick
    • Signing off on all reports - tick
    • Assista and support other CMs - tick
    • Monitor the bounties - 75%
    • Notify Jsgenesis - tick
    • Report on progrees - tick
    • Term summaries - tick

2.3 - Weekly Bounty Managers

  • Reward:
    • Bounty 9: $50 per week
    • Bounty 14: $50 per week
    • Bounty 15: $100 per week
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term + 1 day
    • Start Block: #277200
    • End Block: #392400

Purpose

Keeping track of all bounties is both too much for a single person, and it will require different skillsets. There are currently 4 "weekly" bounties, where "weekly" means that the Bounty Manager isn't meant to have this role until the bounty is completed. Instead, the Council will choose one of their own to act as the Bounty Manager for each bounty during the Term.

Scope of Work

The scope of work for each Bounty will vary quite a lot, depending on the specific bounty.

Some general information can be found here.

Link to Bounties:

After the Council Term has ended, create a brief "handover" report for your successor (even if you are re-elected).

Reward Distribution

Individual. The Council Secretary is responsible for assigning CMs for each Bounty.

Grading

2.4 - Council Surveys

  • Reward: $300
  • Reward Distribution: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #277200
    • End Block: #378000

Purpose

With a new KPI scheme, we need to find out what the issues were, and, if possible, how to address them.

As can be seen from the Annihilation, we also need to know what can be done to increase the "interest" in becoming a Council Member

This is obviously bad, for many reasons, and we want to avoid it happening again.

Scope of Work

Create three surveys, to the groups outlined below:

  1. The previous Council (term ended #277200)
  2. The current Council (term ends #378000)
  3. Members that Announced their candidacy, but weren't elected
  4. "Everyone" else

Define and ask some specific questions, that answer the more high level topics we need information for (target groups):

  • What did you think about the KPIs (1,2)
  • Did the Council co-operate well (1,2)
  • What do you expect your implied "hourly wage" to be after the term (1,2)
  • What made you apply to the Council (1-3)
  • What did you expect "hourly wage" to be before applying (1-3)
  • What did you do get elected (1-3)
  • Did you expect to get elected (1-3)
  • When did you first learn about the Council (1-4)
  • Why did you not apply to the Council (1-4)

The results must be presented in a comprehensive way, with notes to account for possible irregularities, unclear questions/answers, etc.

Notes

  • Simply questions above will not be sufficient to get a full score.
    • You are excepted to break them in to (mostly) multiple choice questions
    • Spend some time thinking about from Jsgenesis POV, and see if you can use the survey to help us create better KPIs, and possibly workflows, through additional questions
  • We will pay 5000tJOY to all members (that was a member before block #219600) answering one or more survey, so make sure they leave their address

Reward Distribution

If multiple surveys are delivered, only the best one will be rewarded. Having said that, co-operation would likely make for a significantly better survey.

Grading

  • Grading defferred as no delivery (will include all contributions when graded)

2.5 - Council Minutes

  • Reward: $200
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #277200
    • End Block: #378000

Purpose

There needs to be some level of accountability and transparency for the Council. For each Term the Council must produce a report, that both summarizes their communication, covers all 'events' and generally explains what transpired during the Term.

Scope of Work

  1. The 2nd "official" Council on Babylon (#118800-#219600) produces a report covering any and all "events" of interest:
  • Proposals
  • Decisions
  • Voting statistics
  • etc.
  1. The Council Produces a "Tokenomics" report covering the quantitative aspects of the Term. Must include:
  • Issuance statistics, through:
    • Spending from proposals
    • Role rewards
    • Bounties paid
    • Validator rewards
    • Total tokens minted
    • Total tokens burned
  • Media statistics
  • Membership statistics
  • Role occupants, their recurring and earned rewards, hired dates, etc.
  • Forum statistics

Previous Council reports can be used as a guideline.

Reward Distribution

If multiple reports are proposed, only the best one will be rewarded.
Ideally however, this would be a collaborative effort.

Grading

2.6 Find All PRs/Issues That Require Jsgenesis Action

  • Reward: $100
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Final day (14400 blocks)
    • Start Block: #363600
    • End Block: #378000

Purpose

As we are often behind on certain issues, and have multiple github repos (and discord) to monitor, assistance is often needed.

We need to compile a list of actions required.

Scope of Work

Towards the end of the term, go through the following repos, and look for open issues and PRs made by someone outside of the "organization", that has not been solved/addressed:

  • joystream
  • helpdesk
  • hydra
  • community-repo
  • atlas
  • founding-members
  • joystream-org
  • handbook

Then, go through the Discord channels (last week only), and add questions/comments that needs to be addressed.

Finally, create an issue in the community repo with a brief TL;DR for each, and a link to the issue/pr.

Note that this issue may be of help, but ensure the items are still not addressed before you make the new issue!

Reward Distribution

If multiple issues are created, only the best one will be rewarded.

Grading

2.7 Discord Channel Management

  • Reward: $50 Per Channel Group
    1. Testnet Roles
    • #validator
    • #storage-provider
    • #content-curator
    • #content-creator
    • #tech-support
    1. Governance
    • #council
    • #proposal
    • #bounties
    1. Newcomers
    • #general
    • #welcome
    • #introduce-yourself
    • #faucet
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term + 1 day
    • Start Block: #277200
    • End Block: #392400

Purpose

To make the Joystream community more welcoming to newcomers on Discord, we need high availability and helpfulness there.

Scope of Work

For each of the above groups (1-3):
Check in multiple times every day, and welcome/assist every user that posts or asks a question. You need to have some knowledge of the particular topic, or read up on it. If you still don't know the answer, tag someone else!

Reward Distribution

Also note that you will "keep" this role for 1 day (14,400 blocks) AFTER the term to allow a new CM to take over.

Grading is individual.

Grading

2.8 Managing the Storage Working Group

  • Reward: $200
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #277200
    • End Block: #378000

Purpose

As the Storage lead is not yet hired, this is a critical task that needs focus.

Scope of Work

In no particular order:

  1. Ensure a new Lead is hired (with stake and rewards).
  2. Create a budget, that calculates the rewards for both the Lead and n workers. This budget must consider:
  • Time spent on hiring, management, performance (spot) checks (Lead only)
  • Actual running costs
  • Set budgets assuming the Lead will hire 5 workers during the Term
  1. Formalize the reporting requirements for the Lead. See helpdesk for details.
  2. Follow up the Lead, and ensure they are performing their work, and hires 3 workers (with stake and rewards).
  3. Ensure the Lead adjusts the workers rewards weekly (as the rate changes)
  4. Sign off on the Leads reports.

Reward Distribution

Grading is individual. If the proposals created in relation to the tasks above are made by different CMs, the rewards will be shared based on the assumed workloads.

Grading

2.9 Manage the Content Curators Working Group

  • Reward: $200
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #277200
    • End Block: #378000

Purpose

Although the working groups Leads are expected to run the day to day, they must be monitored by the Council.

With this KPI, they will also take on a bigger workload.

Scope of Work

In no particular order:

  1. Approve/update the previous budget, that calculated the rewards for both the Lead and n workers. This budget must consider:
  • Time spent on hiring, management, performance (spot) checks (Lead only)
  • Time spent on performing their Curation duties
  • Set budgets assuming there will be a total of 10 Curators at the end of the Term
  1. Formalize/update the reporting requirements for the Lead. See helpdesk for details.
  2. Follow up the Lead, and ensure they are performing their work
  • ensure they have configured curation groups with "appropriate" permissions
  • their reporting duties are maintained
  • a curator is chosen, and performing their duties as, the BM for Bounty #10
  • a curator is chosen, and performing their duties as, the BM for Bounty #18
  1. Ensure the Lead adjusts the workers rewards weekly (as the rate changes)
  2. Sign off on the Leads reports.

Reward Distribution

Grading is individual. If the proposals created in relation to the tasks above are made by different CMs, the rewards will be shared based on the assumed workloads.

Grading

  • @tomato - $40/200
    • management/follow up of WG
    • follow up of bounty #10
    • follow up of hiring
    • follow up of worker rates
  • @oiclid - $50/200
    • managing bounty #10
  • Overall status
    • No new budget approved
    • No reporting requirements
    • Lead has been followed up with and has been performing their work
    • A curator/CM was chosen for bounty #10
    • Bounty #18 isn't active yet
    • Worker rewards appear to be ok
    • No reports

2.10 Proposal Creation

  • Reward: $300
  • Reward Distribution: Shared
  • Grading Process: Automatic
  • Active: Full term
    • Start Block: #277200
    • End Block: #378000

Purpose

Although somewhat related to all the individual KPIs, there seems to be some hesitation to actually creating proposals. Lets reward it!

Scope of Work

This KPI rewards the creator of each proposal that:

  1. Is made by a CM
  2. Gets approved

Reward Distribution

Let:

  • P_c be the number of proposals that gets created by a CM during the term
  • P_a be the number proposals that gets approved during the term
  • P_na be the number proposals is finalized, but not approved, during the term
  • R is the reward
  • *,n is the * for a CM

For each CM:

R,n = R * (P_a,n-P_na,n)/P_c

Grading

Member ID Member Handle Created Approved Reward
361 blackmass 0 0 0
515 l1dev 0 0 0
635 xfactorus 0 0 0
129 anthony 0 0 0
867 xandrell 0 0 0
1962 nkhlghbl 0 0 0
2039 doppelganger23 0 0 0
321 freakstatic_council 1 1 38
957 leet_joy 0 0 0
439 fierydev 0 0 0
552 cheomsk 0 0 0
2 tomato 4 4 150
525 oiclid 3 2 75
319 sparky 0 0 0
1369 lopegor 0 0 0
355 manipal 0 0 0
SUM 16 8 7 262.5

2.11 Council Explainer Video

  • Reward: $300
  • Reward Distribution: Individual
  • Grading Process: Automatic
  • Active: Full term
    • Start Block: #277200
    • End Block: #378000

Purpose

Explainer videos is something we want to have for many different aspects of the platform.

Who is more qualified to make/design one for the Council, than the Council?

Scope of Work

Start by sourcing all the information required to explain the Council for one, or both of these two groups:

  1. Someone that doesn't know anything about the Council
  2. Someone that is trying to get elected or newly elected

Then, make a script and sketches for what these videos should say. Your work will likely be made in to a bounty.

Reward Distribution

If multiple proposals are made, the reward will be split by how much of each is used when the Bounty is created.

Grading

  • Grading defferred as no delivery (will include all contributions when graded)

Round 1

  • KPIs: 8
  • Total Possible Rewards: $2050
  • Council Elected in Round: 2
  • Council Members: 16
  • Term Length: 7 days / 100800 blocks
    • Start Block: #118800
    • End Block: #219600
  • Term Summaries Forum Thread: TBD
  • Deadline to Submit Summary: #248400

Results

Member ID Member Handle Reward [USD] Reward [tJOY]
684 seainvestor 32 809072
361 blackmass 5 126417
515 l1dev 27 682654
318 supunssw 10 252835
2039 doppelganger23 47 1188324
321 freakstatic_council 396 10012261
957 leet_joy 42 1061906
439 fierydev 37 935489
1295 leopold 22 556237
4 nexusfallout 59 1491726
552 cheomsk 50 1264174
2 tomato 643 16257282
1989 2themoon 42 1061906
319 sparky 0 0
1369 lopegor 189 4778579
355 manipal 0 0
SUM 16 1601 40478862

Paid out on block 328850.

1.1 Proposal Clearance

  • Reward: $500
  • Reward Distribution: Shared
  • Grading Process: Automatic
  • Active: Full term
    • Start Block: #118800
    • End Block: #219600

Purpose

For the governance process to function properly, all proposals must be processed effectively, and dealt with within a reasonable time frame. Although we have increased number of proposals that can be open at any time from 5 to 20, it is still important that the community gets a quick result when possible.

This means the Council should be quick to vote when possible, and ask clarifying questions when information is missing.

Scope of Work

For the individual Council Member, this means that they must check in frequently, and address each open proposal. If what is presented is reasonable and within the budget, the proposal should in general be approved.

Of course, the Councils time must be respected, in the sense that the proposal should contain all the information needed to make their verdict. If this is not the case, the proposal discussion system can be used to ask for what is missing.

Without going in too much detail:

  • Most proposals will be of type Text or Spending. Along with some of the Working Group proposals, these should also be the most straight forward to vote on.
  • If the Spending proposal is for a Bounty, make sure the formalities, (eg. ask the Bounty Manager) are in order before casting your vote.
  • If you have all the information you need, vote right away.
  • Regardless of your decision, you should also make a brief comment outlining your reasoning.
  • If you don't have all the information, or don't fully understand, check the comments to see if it has already been addressed. If it hasn't, ask!
  • If you are not sure, you can always:
  • ask in the discussion
    confer with other CMs on Discord and/or the forum
  • if so, this should be linked to or summarized in the discussion
  • vote abstain

Reward Distribution

After the Term is over, we will get all the voting data from the proposals that was open during the Term. The reward will be divided by the number of total proposals.

  • Each time a CM voted for a proposal, they earn 1 point.
  • If they voted the same as the final outcome, they earn 3 more points.
  • If they voted abstain, they also earn 3 more points - as long as they didn't vote abstain on more than 20% of the total proposals.
  • Finally, the first 2 CMs that vote, AND vote "correctly" earns 2 more points.

The CMs reward for each proposal will be proportional to their points.

Note
Once a proposal is finalized, voting stops, so if you want to "piggyback" on the others, you may find yourself not getting to vote in time.

Grading

Member ID Member Handle Voted Points Reward [USD]
684 seainvestor 22 79 32
361 blackmass 3 12 5
515 l1dev 17 66 26
318 supunssw 7 25 10
2039 doppelganger23 26 95 38
321 freakstatic_council 33 125 50
957 leet_joy 28 106 42
439 fierydev 23 89 36
1295 leopold 13 52 21
4 nexusfallout 31 114 46
552 cheomsk 33 121 48
2 tomato 32 154 62
1989 2themoon 23 86 34
319 sparky 0 0 0
1369 lopegor 33 124 50
355 manipal 0 0 0
SUM 16 324 1248 500

1.2 - Council Secretary

  • Reward: $300
  • Reward Distribution: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #118800
    • End Block: #219600

Purpose

Although this is not a formal role on the platform, having someone responsible for co-ordinating the Council is needed.

The role should be occupied by a "seasoned" Council Member that:

  • is well versed in the platform workings
  • is familiar with github
  • has high availability

Scope of Work

The Council Secretary will act as a bridge between the Council and Jsgenesis. This means:

  • Assigning Jsgenesis to review* all PRs made to the Community Repo, with a link to the spending proposals and other applicable information.
  • Signing off on all reports created
  • Assist and support other CMs
  • Monitor the bounties
    • propose/hire Bounty Managers, set their rewards and secure funding after the fact
    • follow up Bounty Managers (and replace if needed)
    • select the "Weekly Bounty Managers" ref 1.3, according to interest (they will be paid through KPI rewards)
    • ensure the bounty information presented on the website is up to date
    • report on progress after the end of the Term
  • Notify Jsgenesis of urgent and important matters on the testnet
  • Open a forum thread for the "Term Summaries" where the CMs can report on their Council/KPI activities.

* Not before all formalities has been completed, eg. approved by the Council

Reward Distribution

Although a single person has the final responsibility, the Council may choose to elect a back-up, deputy, or split the work between bounties and non-bounties.

Grading

  • @tomato - $280/$300
    • [x] Assigning Jsgenesis community repo review
    • [x] Signing off on all reports
    • [x] Assist and support other CMs
    • [x] Monitor the bounties - 75%
    • [x] Notify Jsgenesis
    • [x] Report on progrees
    • [x] Term summaries

1.3 - Bounty Managers

  • Reward:
    • Bounty 9: $50 per week
    • Bounty 10: $50 per week
    • Bounty 14: $50 per week
    • Bounty 15: $100 per week
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term + 1 day
    • Start Block: #118800
    • End Block: #234000

Purpose

Keeping track of all bounties is both too much for a single person, and it will require different skillsets. There are currently 4 "weekly" bounties, where "weekly" means that the Bounty Manager isn't meant to have this role until the bounty is completed. Instead, the Council will choose one of their own to act as the Bounty Manager for each bounty during the Term.

Scope of Work

The scope of work for each Bounty will vary quite a lot, depending on the specific bounty.

Some general information can be found here.

Link to Bounties:

Reward Distribution

Individual. The Council Secretary is responsible for assigning CMs for each Bounty.

Grading

1.4 - Council Reporting

  • Reward: $250
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #118800
    • End Block: #219600

Purpose

In order for the Council to perform their reporting requirements (as described in KPI 1.5), any tools and scripts must, at least, be updated to use the new types.

Scope of Work

  1. Update the "Tokenomics" script in the Community Repo,
  2. Produce the "Tokenomics" report covering the quantitative aspects of the Term. Must include:
  • Issuance statistics, ie:
    • Spending from proposals
    • Role rewards
    • Bounties paid
    • Validator rewards
    • Total tokens minted
    • Total tokens burned
  • Media statistics
  • Membership statistics
  • Role occupants, their recurring and earned rewards, hired dates, etc.
  • Forum statistics
  • etc.

Reward Distribution

If multiple scripts and reports are proposed, only the best one will be rewarded.

Grading

  • @freakstatic_council - $220/$250
    • https://github.com/Joystream/community-repo/pull/169
      • [x] Spending from proposals
      • [x] Role rewards
      • [x] Bounties paid
      • [x] Validator rewards
      • [x] Total tokens minted
      • [x] Total tokens burned
      • [x] Media statistics
      • [x] Membership statistics
      • [x] Role occupants
      • [ ] Reccuring and earned role rewards
      • [ ] Hired dates - no
      • [x] Forum statistics

1.5 - Council Minutes

  • Reward: $200
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #118800
    • End Block: #219600

Purpose

There needs to be some level of accountability and transparency for the Council. For each Term the Council must produce a report, that both summarizes their communication, covers all 'events' and generally explains what transpired during the Term.

Scope of Work

  1. The first "official" Council on Babylon (#118800-#219600) produces a report covering any and all "events" of interest:
  • Proposals
  • Decisions
  • Voting statistics
  • etc.
  1. The Council Produces a "Tokenomics" report covering the quantitative aspects of the Term. Must include:
  • Issuance statistics, through:
    • Spending from proposals
    • Role rewards
    • Bounties paid
    • Validator rewards
    • Total tokens minted
    • Total tokens burned
  • Media statistics
  • Membership statistics
  • Role occupants, their recurring and earned rewards, hired dates, etc.
  • Forum statistics

Previous Council reports can be used as a guideline.

Reward Distribution

If multiple reports are proposed, only the best one will be rewarded.
Ideally however, this would be a collaborative effort.

Grading

1.6 Find All PRs/Issues That Require Jsgenesis Action

  • Reward: $100
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #118800
    • End Block: #219600

Purpose

As all of our attention was focused on debugging the babylon failure, then getting antioch up and running, we haven't been very responsive on Github lately.

We need to compile a list of actions required.

Scope of Work

Go through the following repos, and look for open issues and PRs made by someone outside of the "organization", that has not been solved/addressed:

  • joystream
  • helpdesk
  • hydra
  • community-repo
  • atlas
  • founding-members
  • joystream-org
  • handbook

Then, create an issue in the community repo with a brief TL;DR for each, and a link to the issue/pr.

Grading

  • @tomato - $100/100

1.7 Discord Channel Management

  • Reward: $100 Per Channel Group
    1. Testnet Roles
      • #validator
      • #storage-provider
      • #content-curator
      • #content-creator
      • #tech-support
    2. Governance
      • #council
      • #proposal
      • #bounties
    3. Newcomers
      • #general
      • #welcome
      • #introduce-yourself
      • #faucet
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term + 1 day
    • Start Block: #118800
    • End Block: #234000

Purpose

To make the Joystream community more welcoming to newcomers on Discord, we need high availability and helpfulness there.

Scope of Work

For each of the above groups (1-3):

  1. Create a draft "channel topic" description, with relevant information and links (if applicable).
  2. Check in multiple times every day, and welcome/assist every user that posts or asks a question. You need to have some knowledge of the particular topic, or read up on it. If you still don't know the answer, tag someone else!

Reward Distribution

The first CM that gets an approved Text proposal that includes the draft of the various "channel topics" are assigned that group. Note that $100 will only apply for the "full" 7 days (100,800 blocks), so if the Text proposal is approved after block #133200, your reward will decrease proportionally.

Also note that you will "keep" this role for 1 day (14,400 blocks) AFTER the term to allow a new CM to take over.

Grading is individual.

Grading

1.8 Managing the Working Groups

  • Reward: $150 per Working Group
    1. Content Curators
    2. Storage Providers
  • Reward Structure: Individual
  • Grading Process: Manual
  • Active: Full term
    • Start Block: #118800
    • End Block: #219600

Purpose

As we have yet to elect new leads, and set new budgets for the Working Groups, this is a critical task that needs focus.

Scope of Work

For each of the two Working Groups (in no particular order):

  1. Ensure a new Lead is hired for both roles (with stake and rewards).
  2. Create a budget, that calculates the rewards for both the Lead and n workers. This budget must consider:
    • Actual running costs (mostly for SPs)
    • Time spent on performing their duties (mostly for CCs, but also SP lead)
    • Set budgets assuming the Lead will hire 5-15 workers for each role
  3. Formalize the reporting requirements for the Lead. See helpdesk for details.
  4. Follow up the Lead, and ensure they are performing their work, and starts hiring at least 3 workers each (with stake and rewards).
  5. Sign off on the Leads reports.

Reward Distribution

Grading is individual. If the proposals created in relation to the tasks above are made by different CMs, the rewards will be shared based on the assumed workloads.

Grading