Merge pull request #119 from mochet/wgreport

WG Report + Tasks

workinggroup-reports/KPI_12_WG_reports/wg_tasks.md

@@ -0,0 +1,14 @@
+## Storage WG Tasks
+
+1. What is the storage capacity of each individual server now?
+2. Is it possible to show how much bandwidth each server has consumed over the past week or month? If there are no tools installed for this currently, it may be possible to get this information from the server host (ex. Vultr shows the bandwidth use of each server on a daily basis going back a month)
+3. What are the approximate costs of each server, and do the current worker payments cover these?
+
+
+## Curator WG Tasks
+
+1. Hire 2 curator workers during the council session, preferably at least one bilingual curator as we have a lot of Russian language content that has to be reviewed. Make sure the openings for these have clear deadlines as we have a backlog of uncurated videos.
+2. Once hired, post a thread on the forums indicating the language/timezone of the curation team
+3. Since it is assumed there are many uncurated videos, prioritize getting outstanding videos curated.
+4. Create a thread and complete one regular check as defined here: https://github.com/Joystream/helpdesk/tree/master/roles/content-curators#regular-checks. Since no check has been performed before this could include the videos uploaded since the last curation work was performed.
+5. Post on the forums or create a proposal with a basic breakdown of the status of the working group, this should include a status of uncurated videos at the end of the council session.

workinggroup-reports/KPI_12_WG_reports/working_group_followup.md

@@ -0,0 +1,26 @@
+## Council Status
+Before we talk about the status of the working groups its important to note also the status of the council and platform in general:
+* The Council has only agreed on a reporting system for the Storage working group, the council hasn't agreed on one for the Curator working group so far.
+* The Council is lagging behind a bit with voting on proposals and submitting proposals for WGs (such as mint refill requests) has probably been quite difficult recently.
+
+## Storage Working Group Status
+The current status of this working group:
+* The lead had been following the reporting requirements reasonably well
+* Only one storage provider has responded to the tasks agreed upon by the council: https://testnet.joystream.org/#/forum/threads/319 (this will be reviewed separately to this report)
+* The workers are being paid and their storage providers are up
+* One worker has reported that the total content storage size plus blockchain size has meant they are utilizing 175GB out of 195GB capacity, this means a budget increase for this working group is necessary in the very near future.
+* I've run HELIOS and it indicates all providers are up and the content directory is fully replicated.
+
+## Curator Working Group Status
+The current status of this working group:
+* The lead is responsive on the forums / chat
+* The group seems to have accomplished most of the tasks agreed on by the council: https://testnet.joystream.org/#/forum/threads/320 (this will be reviewed separately to this report)
+* The lead has hired two workers
+* The group overall seems to be progressing quite well with work and has produced several threads on the forums and is also working on Discord to communicate to content creators about issues.
+* No communication has been made via the forums regarding workload or the number of workers, so it assumed that this is sufficient for now.
+
+
+## Notes for future councils
+* The Storage working group needs a budget increase, the amount of this has yet to be determined. We have some budget capacity for this.
+* The Council needs to agree on an updated reporting requirement for the Storage WG that takes into account the total storage capacity and when they are likely to be exceeded.
+* The Council needs to agree on reporting requirements for the Curator WG.

workinggroup-reports/KPI_12_WG_reports/working_group_status.md

@@ -0,0 +1,24 @@
+## Council Status
+Before we talk about the status of the working groups its important to note also the status of the council and platform in general:
+* The Council has only agreed on a reporting system for the Storage working group, the council hasn't agreed on one for the Curator working group so far.
+* There has been a huge number of new users making communication with the working groups less than ideal
+* We've recently transitioned from Telegram to Discord so communication has not been ideal
+* We've had a significant number of uploads in a short amount of time due to so many new users and there aren't really any processes we've developed so far to deal with this level of activity.
+
+## Storage Working Group Status
+The current status of this working group:
+* The lead is responsive on the forums / chat (although was unresponsive for a bit)
+* The lead had been following the reporting requirements reasonably well
+* All of the storage providers seem to have enough storage capacity to host the content directory as it currently stands (108 GB). I've created a thread to ask about this and point out how to access the size information from https://status.joystream.org/status : https://testnet.joystream.org/#/forum/threads/299
+* The workers are being paid and their storage providers are up
+* There appear to be sufficient workers hired for this role and the maximum allowed for by the budget, no requests have been made to increase this number yet.
+
+## Curator Working Group Status
+The current status of this working group:
+* The lead is responsive on the forums / chat
+* The lead has been having issues with the CLI (it has had to be reinstalled and is taking time to reinstall)
+* The only curator worker has quit
+* There was one worker, however a budget was approved for two workers.
+* There is no clear reporting system in place and since there is no reporting system in place we can't identify how many videos require curation.
+* There is evidently a backlog of videos requiring curation that are affecting new users of the platform. It is unclear how big the backlog of videos is and Atlas shows the last video uploaded as being from 3 days ago.
+* It is unclear what tools (besides just the CLI) are available or need to be created to allow for effective reporting for this role.