Merge pull request #11 from mochet/master

Adding new council report + previous council reports

council-reports/Council Round #17 - 07-08-2020 - Council Report.md

@@ -0,0 +1,161 @@
+# Council Round #17 - 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 Round: #17
+Start Block: #2046811
+End Block: #2147610
+Start time/date: 07.08.2020 ~18:00 GMT
+Forum thread for round feedback: https://testnet.joystream.org/#/forum/threads/89?replyIdx=8
+
+### 1.3 - Council members
+Council Members (Member name, Key)
+@hskang9 - 5Cm5sPqHbFnTLBRxLYwFGvyq1BwtsYiUed1wKrfc92pjND4D
+@titan - 5CtJTw9gT3gVKPYUryz8bWu5M1tWfdXrejbxvpDkfydrMERE
+@blackmass - 5CunuuAenxcL2U9bmbXzWSwFMTv8Z8WhudSJjRVknU2fSAXC
+@supunssw - 5EZxuZgXdk82cDM24Sxon4ToPDqFdsG526yvnc96WQJi6wTC
+@jimmy_tudeski - 5EnTgQjJhzKSd4Fz8bsyRjRYiLcH24DX5ahK156CFJ9FvTT8
+@tomato - 5FnXBHfcDE6nQrwHjZqHYYpnzCLap2b9d3eQHt2Jt9eBG6mv
+@rmbangera1983 - 5GJKUAC6CowjvLhUVkX9aSZGAY6eCu8BU5WCNzkDNduQrUMc
+@branko123 - 5GW1DZaHCxgvHegLQqcKppWtvAYRd5fu7Si9boHakpLKGr91
+@sieemma - 5HWKe5kQKPuKopnWkfwMdULGNsZimaxaLv7HuHjfy2yir3f1
+@jstream - 5HhN69rptX3Nm4DMSmCoJ6SCfpQarBSBGVXKDCgQNf1JtMq5
+
+## 2 - Minutes
+### 2.1 - Proposal Overview
+- 9 Proposals Created
+	- 5 Spending Proposals
+	- 1 FillWorkingGroupLeaderOpening Proposal
+	- 3 Text Proposals
+
+- 6 Approved & executed proposals
+- 1 NotEnoughCapacity failure
+- 1 canceled
+- 1 expired
+
+Total time for proposals to finalize: 497.37 hours
+Average time for proposals to finalize: 55.26 hours
+	This average is calculated from all proposals, including canceled and expired proposals.
+
+### 2.2 - Basic Budget
+- 5 Spending Proposals
+	- Total amount paid out by council: 8684863 tJOY
+
+### 2.3 - Proposal Breakdown
+#### Proposal 44 - Spending Proposal for Telegram Bot KPI
+- Proposal Link: https://testnet.joystream.org/#/proposals/44
+- Proposal Type: Spending 
+- Status: Approved & executed successfully
+	- Time to finalize: 29,846 blocks (49.74 hours)
+- Created by: @enjoythefood
+- Participants: @branko123, @sieemma, @jimmy_tudeski, @titan, @tomato, @blackmass
+#### Proposal 45 - Spending Proposal for Telegram Bot KPI 2
+- Proposal Link: https://testnet.joystream.org/#/proposals/44
+- Proposal Type: Spending
+- Status: Approved & executed successfully
+	- Time to finalize: 36,016 blocks (60.02 hours)
+- Created by: @enjoythefood
+- Participants: @branko123, @jimmy_tudeski, @titan, @tomato, @blackmass, @rmbangera1983
+#### Proposal 46 - Spending Proposal for Telegram Bot KPI 3
+- Proposal Link: https://testnet.joystream.org/#/proposals/44
+- Proposal Type: Spending
+- Status: Approved & executed successfully
+	- Time to finalize: 37,748 blocks (62.91 hours)
+- Created by: @enjoythefood
+- Participants: @branko123, @jimmy_tudeski, @titan, @tomato, @hskang9, @rmbangera1983
+#### Proposal 47 - Spending Proposal for Telegram Bot KPI 4
+- Proposal Link: https://testnet.joystream.org/#/proposals/44
+- Proposal Type: Spending
+- Status: Failed (NotEnoughCapacity)
+	- Time to finalize: 37,931 blocks (63.21 hours)
+	- This was remedied via sudo action by @bwhm0
+- Created by: @enjoythefood
+- Participants: @branko123, @supunssw, @jimmy_tudeski, @titan, @tomato, @rmbangera1983
+#### Proposal 48 - Spending Proposal for Telegram Bot KPI 5
+- Proposal Link: https://testnet.joystream.org/#/proposals/44
+- Proposal Type: Spending
+- Status: Approved & executed successfully
+	- Time to finalize: 31,560 blocks (52.60 hours)
+- Created by: @enjoythefood
+- Participants: @branko123, @jimmy_tudeski, @titan, @tomato, @blackmass, @rmbangera1983
+#### Proposal 49 - Fill storage lead
+- Proposal Link: https://testnet.joystream.org/#/proposals/44
+- Proposal Type: FillWorkingGroupLeaderOpening
+	- Role: Storage Lead
+	- Previous Candidate: N/A
+	- Payment: 4315 tokens / 600 blocks
+	- Candidate: @rajcprem
+- Status: Approved & executed successfully
+	- Time to finalize: 6,951 blocks (11.58 hours)
+- Created by: @tomato
+- Participants: @branko123, @jimmy_tudeski, @titan, @tomato, @blackmass, @rmbangera1983
+#### Proposal 50 - Proposal to "Overhaul" the KPI System
+- Proposal Link: https://testnet.joystream.org/#/proposals/44
+- Proposal Type: Text
+	- Time to finalize: 5,761 blocks (9.60 hours)
+- Forum thread: 
+- Status: Approved & executed successfully
+- Created by: @joystream
+- Participants: @branko123, @sieemma, @supunssw, @jimmy_tudeski, @titan, @jstream
+#### Proposal 51 - Create a help & support forum category
+- Proposal Link: https://testnet.joystream.org/#/proposals/44
+- Proposal Type: Text
+- Status: Canceled
+	- Time to finalize: 40,441 blocks (67.71 hours)
+- Created by: @tomato
+- Participants: @sieemma, @jimmy_tudeski, @titan, @nexusfallout, @tomato, @blackmass
+#### Proposal 52 - Use Forum as primary community platform
+- Proposal Link: https://testnet.joystream.org/#/proposals/44
+- Proposal Type: Text
+- Status: Expired
+	- Time to finalize: 72,000 blocks (120 hours)
+	- Due to a system limitation this proposal allowed votes to occur beyond this council session, the votes are included here. As the proposal was not withdrawn the current proposal system means the proposal becomes impossible to be approved regardless of voter quorum.
+- Created by: @bedeho1
+- Participants: @sieemma, @supunssw, @warrior, @fierydev, @jimmy_tudeski, @titan, @nexusfallout, @sparky, @tomato, @blackmass
+ 
+### 2.2 - Community Repo Pull Requests
+- https://github.com/Joystream/community-repo/issues/9
+	- https://testnet.joystream.org/#/forum/threads/49
+	- PR + forum thread created for Council Minutes & Performance Review
+	- Participants: @tomato, @fierydev, freakstatic_council
+
+### 2.3 - Select events
+- Storage lead elected
+	- Proposal: https://testnet.joystream.org/#/proposals/44
+	- Finalized at block: 2055338
+- Telegram Bot delivered and launched
+	- Proposal: https://testnet.joystream.org/#/proposals/44
+- KPI system overhaul initiated
+	- Proposal: https://testnet.joystream.org/#/proposals/44
+
+## 3 - Review
+### 3.1 - Workflow, Performance, Challenged & Thinking
+@tomato
+This council round had a few issues, mostly to do with council member activity. There were 5 proposals made to pay for the Telegram bot, but this completely filled up the allowed number of proposals, which delayed other proposals from being made. This was a big issue as the storage lead had already taken a significant amount of time and meant that our current set of storage workers had not been running storage nodes for quite some time, we should try to avoid this at all costs in the future because the community is very small and huge gaps in inactivity can make people become bored of contributing further. We also began using signal proposals to refill the council mint, this may take some time to be more effectively used, but I think we should try to aim for refilling the council mint in 2 week intervals. If the council mint is empty it not only means that spending proposals won't work, but also that council members won't be paid.
+The KPI improvement proposal was voted through successfully but no council member submitted an improved proposal as required by the actual KPI, it seems we need to work on better communicating the KPIs to the council members in some way, for now I manually highlight some in the Telegram channel but it doesn't look as if council members are looking directly at these when needed. Two proposals failed due to CM inactivity, but these were submitted towards the end of the council term. The only option right now is for the creator of a proposal like this to withdraw (which costs tokens) are resubmit immediately after the new council begins. This is not ideal but is a system limitation for now that will need to be addressed in the future as it makes the later stages of the council term problematic for submitting proposals.
+Currently we also have a backlog of work that the council should be taking care of. The 3 main areas of this are council reports, tokenomics reports and the community repo. With the new council secretary role these may be taken care of. The biggest gap right now is the tokenomics report which requires a bit of technical understanding to complete, but once the script has been created should be the easiest report to produce each week. We may have to look at discussing better incentives to get the tokenomics report completed.
+
+## 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 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.
+- Content Curator Mint
+	- The Content Curator Mint currently has a maximum value of 1 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 1 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
+- There are no outstanding bounties at this time.

council-reports/Council Round #8 - 12-06-2020 - Council Report.md

@@ -0,0 +1,84 @@
+# Council Performance Review and Minutes
+## 1 - Basic Information
+Council #8 blocks: 1,139,611‬-1,240,411‬ (second council)
+The council is expected to produce reports during each round and provide feedback in the form of workflow, challenges, thinking and performance.
+
+Usernames referenced are Joystream usernames.
+
+## 2 - Minutes
+### 2.1 - Proposals Created
+- Create a Community Wishlist (https://testnet.joystream.org/#/proposals/12)
+     - Forum thread: https://testnet.joystream.org/#/forum/threads/44
+	 - Status: Passed (execution failed due to council mint being depleted)
+	 - Created by: @tomato
+	 - Participants: (there is a UI bug so I cannot see who voted on this)
+- v6.15.0 - Enable Proposals Discussions (https://testnet.joystream.org/#/proposals/13)
+     - Forum thread: N/A
+     - Status: Passed (cancelled during grace period due to bugs)
+     - Created by: @joystream
+     - Participants: @warrior, @freakstatic_council, @fierydev, @tomato, @sparky
+- v6.15.0 - Proposal Discussion #2 (https://testnet.joystream.org/#/proposals/14)
+     - Forum thread: https://testnet.joystream.org/#/forum/threads/45
+	 - Status: Passed (pending execution)
+	 - Participants: @warrior, @enjoythefood, @anthony, @freakstatic_council, @fierydev, @tomato, @sparky
+- Fire Jsgenesis Storage Provider (https://testnet.joystream.org/#/proposals/15)
+     - Forum thread: https://testnet.joystream.org/#/forum/threads/48
+     - Discussed via Telegram
+     - Created by: @bwhm0_2
+     - Voters: @enjoythefood, @freakstatic_council, @fierydev, @tomato, @sparky
+
+### 2.2 - Github Issues Created
+- https://github.com/Joystream/joystream/issues/689
+	- Github issue created regarding council reward issues (@tomato)
+- https://github.com/Joystream/joystream/issues/670
+	- Github issue created regarding runtime proposal page lag (@tomato)
+
+### 2.3 - Community Repo Pull Requests
+- https://github.com/Joystream/community-repo/pull/2
+- https://testnet.joystream.org/#/forum/threads/43
+	- PR + forum thread created for initial template of Tokenomic + Network report 
+	- Participants: @tomato, @freakstatic_council
+- https://github.com/Joystream/community-repo/pull/3
+- https://testnet.joystream.org/#/forum/threads/44
+	- PR + forum thread created for community wishlist
+	- Participants: @tomato
+- https://github.com/Joystream/community-repo/pull/4
+- https://testnet.joystream.org/#/forum/threads/42
+	- PR + forum thread created for first version of KPI 2.4 - State of The Network Reporting
+	- Participants: @freakstatic_council, @enjoythefood, @tomato, @fierydev
+
+### 2.4 - Select Forum Activity
+- https://testnet.joystream.org/#/forum/threads/46
+	- Thread created to detail the current status of the Council Mint & instructions for how to check it and request a refill.
+	- Participants: @tomato
+- https://testnet.joystream.org/#/forum/threads/49
+	- Thread created to solicit feedback for this document
+	- Participants: @tomato, @fierydev, @freakstatic_council
+
+### 2.5 - Select events
+- Council mint depleted
+	- Notified Jsgenesis
+	- Participants: @tomato
+
+## 3 - Review
+### 3.1 - Workflow
+@fierydev
+Firstly, voting is not just easy, but quite pleasant. No issues in the way/method of voting.
+
+@tomato
+Most of the proposals were fairly straight forward, except the community wishlist which requires the discussion system before being added.
+
+### 3.2 - Challenges & Thinking
+@fierydev
+The only major issue in the above mentioned proposals was for the runtime upgrades, as you are already aware of the lag/loading issue. It can get as bad as I couldn't vote for 15 minutes, had to give up and voted some hours later. The only other minor improvement would be maybe a post for every proposal made with some sort of description so Council can make more of an informed choice. A good example would be Proposal #15 to fire StorageProvider, I didn't know why we were firing them, had to confirm on telegram before I could vote. (This might be a one time issue I faced as it was my first term and I wasn't aware of the details - If anyone else faced same issue, please corroborate or confirm)
+
+@freakstatic_council
+This round was a bit about getting the information for the KPI reports of the previous rounds and for the curator lead prepare things for the curators to work.
+We didn't tried the new proposal discussion system which was added this round.
+
+@tomato
+I think one of the issues we're having is a lack of participation by some council members, in order for people to vote for council members they have faith in, we need to increase engagement. We might be able to improve on this by attributing contributions on this report with the author's name, this would show people who is contributing. I also think there is a lack of people using the spending proposal, we should be aiming to have more spending proposals and using the council's ability to fund things to drive user engagement on the platform. There are several things that the council could fund, but its a chicken and egg problem, because spending proposals come when someone wants to contribute, but we need to have better awareness of what bounties are available, and what are sensible amounts for bounties. The UI/UX of the council page is very hard to understand, there are already improvements in the pipeline, but at the moment it creates some challenge in understanding the status of things.
+
+### 3.3 - Performance
+@tomato
+Overall council members voted on proposals appropriately, but the level of engagement can be improved upon. The proposal discussion system will launch soon, so we will be able to see if that tool increases the level of participation. There is a big difficulty in accessing information from the blockchain, and the tools required to get this information in easier formats are time consuming to create and manage. I would expect that once more tools become available (like reports) the council will be able to work better. One area the council is lacking in, is effectively using the funds it controls (meaning any funds that are added to the dollar backing of the platform after you pay for all the roles). This requires having more users on the platform as well, but eventually we should be aiming to use some of these funds to improve resources, tools and documentation for things that aren't covered by Jsgenesis.

council-reports/Council Round #9 - 19-06-2020 - Council Report.md

@@ -0,0 +1,115 @@
+# Council Performance Review and Minutes
+## 1 - Basic Information
+
+Council #9 blocks: 1,240,411 - 1,341,211 (fourth council)
+
+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.
+
+## 2 - Minutes
+### 2.1 - Proposals Created
+- Fund the forum sudo account (https://testnet.joystream.org/#/proposals/16)
+     - Forum thread: https://testnet.joystream.org/#/forum/threads/56
+	 - Status: Approved & executed successfully
+	 - Created by: @tomato
+	 - Participants: @enjoythefood, @freakstatic_council, @warrior, @fierydev, @sparky, @tomato
+ - Council #8 Report (https://testnet.joystream.org/#/proposals/17)
+	 - Forum Thread: https://testnet.joystream.org/#/forum/threads/49
+	 - Github PR: https://github.com/Joystream/community-repo/pull/5
+	 - Status: Approved
+	 - Created by: @tomato
+	 - Participants: @enjoythefood, @freakstatic_council, @warrior, @fierydev, @tomato, @anthony
+ - Elect a Forum Sudo Key (https://testnet.joystream.org/#/proposals/18)
+	 - Forum Thread: https://testnet.joystream.org/#/forum/threads/56
+	 - Status: Approved
+	 - Created by: @tomato
+	 - Participants: @enjoythefood, @warrior, @fierydev, @sparky, @tomato, @anthony
+ - 15.06.2020 - Test Proposal Discussion (https://testnet.joystream.org/#/proposals/19)
+	 - Forum Thread: N/A (discussion system was activated, so any proposals after this do not require a dedicated forum thread)
+	 - Status: Slashed
+	 - Crated by: @tomato
+	 - Participants: @enjoythefood, @freakstatic_council, @fierydev, @sparky, @tomato, @alex_m
+ - 15.06.2020 - Storage Node payment update (https://testnet.joystream.org/#/proposals/20)
+	 - Forum threads: https://testnet.joystream.org/#/forum/threads/57 & https://testnet.joystream.org/#/forum/threads/32
+	 - Status: Approved & Executed
+	 - Created by: @tomato
+	 - Participants: @enjoythefood, @freakstatic_council, @warrior, @fierydev, @sparky, @tomato, @anthony
+ - Replenishing the mind tor ContentCurator (https://testnet.joystream.org/#/proposals/21)
+	 - Forum threads: N/A
+	 - Status: Approved
+	 - Created by: @maks_malensek
+	 - Participants: @enjoythefood, @freakstatic_council, @warrior, @fierydev, @sparky, @tomato
+ - 14.06.2020 council payments (manual) (https://testnet.joystream.org/#/proposals/22)
+	 - Forum threads: https://testnet.joystream.org/#/forum/threads/60
+	 - Status: Approved
+	 - Created by: @tomato
+	 - Participants: @enjoythefood, @bradt, @fierydev, @sparky, @tomato, @anthony
+ - Reqs for creating new forum categories
+ 	- Forum thread: N/A
+	- Status: Approved
+	- Created by: @tomato
+	- Participants: @freakstatic_council, @fierydev, @sparky, @tomato, @anthony, @alex_m
+
+### 2.2 - Community Repo Pull Requests
+- https://github.com/Joystream/community-repo/pull/5
+- https://testnet.joystream.org/#/forum/threads/49
+	- PR + forum thread created for Council Minutes & Performance Review
+	- Participants: @tomato, @fierydev, freakstatic_council
+
+### 2.3 - Select Forum Activity
+- https://testnet.joystream.org/#/forum/threads/56
+	- Thread created for KPI 4.6 - Forum Sudo
+	- Participants: @tomato, @fierydev, @enjoythefood, @maks_malensek, @freakstatic_council
+- https://testnet.joystream.org/#/forum/threads/57
+	- Thread created for discussing storage provider payment updates
+	- Participants: @tomato, @freakstatic_council
+- https://testnet.joystream.org/#/forum/threads/58
+	- Thread created for discussing KPI 4.1 - Block Production
+	- Participants: @tomato, @freakstatic_council
+- https://testnet.joystream.org/#/forum/threads/59
+	- Thread created for discussing this document and soliciting council feedback
+	- Participants: @tomato, @freakstatic, @fierydev
+- https://testnet.joystream.org/#/forum/threads/60
+	- Thread created for resolving manual council payments
+	- Participants: @tomato, @freakstatic_council
+
+### 2.5 - Select events
+- Runtime Updated (proposal discussion system became active)
+	- Proposal: https://testnet.joystream.org/#/proposals/14 (passed during previous council)
+	- Block: 1,279,512
+- Council member payment issues
+	- There are some issues with council payments and they need to be done manually, discussion about this and a proposal was created.
+
+## 3 - Review
+### 3.1 - Workflow
+@tomato
+During this council round, the proposal discussion system was activated which makes the council's processes a lot more streamlined. Most of the workflow for now involves trying to create a discussion regarding proposals and then finally creating proposals and trying to get the council to vote in a timely fashion.
+@freakstatic
+I also agree that this round was bit difficult to get most of the members contribute to the council, right from the start it took a bit to gather the 10 participants required to fill the council seats. Maybe in the future the number of seats can be reduce in order to include only interested/active members but is a bit too soon to decide.
+@fierydev
+Hi, not much feedback for this round, from what I can understand, the council has been quite actively trying to figure out the next set of KPI's and how to full fill them! Meaningful ideas are being exchanged by many learned members and progress is being made.
+### 3.2 - Challenges & Thinking
+@tomato
+For this round of the council it was very difficult to get the majority of the council to vote on proposals in a timely fashion, however no proposals failed due to a lack of votes, but it could still be improved. This was probably due to the poor turnout (10 applicants for 10 seats) for the previous election and perhaps newer members of the council are not fully aware of the council's role on the platform. Besides activity of members some of the KPIs were difficult to achieve within the timeframes expected.
+@freakstatic
+The number of validators have been a bit low lately... Maybe we should increase the reward or decrease the available slots.
+### 3.3 - Performance
+@tomato
+Overall the council did well this round in creating proposals and communicating across various mediums (forum & Telegram chat). Unfortunately we missed some KPIs this session due to various reasons.
+@fierydev
+Sufficient votes for deciding proposals are being made in a not so timely manner, however I feel that the new Council will be doing a better job this week!
+
+## 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 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.
+- Content Curator Mint
+	- The Content Curator Mint currently has a maximum value of 1 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.
+### 4.2 Bounties
+- Forum Telegram Bot Bounty ($60)
+	- This was already coded and implemented but the author has not yet created a spending propsal to collect their reward. The author should commit the code to Joystream community repo when they are ready to collect the reward. (https://testnet.joystream.org/#/forum/threads/33)