Merge pull request #213 from maxlevush/master

WG Lead Term Limits and Storage WG Lead - Tasks + Reporting Requirements

rules/Storage_WG_Lead-Report_and_Tasks.md

@@ -0,0 +1,28 @@
+# Storage WG Lead - Tasks + Reporting Requirements
+
+*Pre-proposal Discussion https://testnet.joystream.org/#/forum/threads/370, https://testnet.joystream.org/#/forum/threads/461*
+
+*Based on the KPIs https://blog.joystream.org/sumer-kpis/#10.7*
+
+### Storage WG Lead requested to report once a week 
+- this report should include a spotcheck that each provider is working (checking through Atlas or some other means).
+- A run of HELIOS
+- A full breakdown of system specs for each storage provider
+- Bandwidth use on each provider
+- Periodic upload tests
+- Free space of each one of the storage workers
+
+### Additional tasks
+
+- The Lead must adjust the workers rewards if required due to rate changes.
+- The Lead should fire and/or slash non-performing workers.
+- Lead (and/or other SPs) must be available and helpful in Discord and the forum.
+- Identify storage providers that have low download speed or other issues, and warn the providers.
+
+If Lead missed the report - he can be warn/fire/slash https://testnet.joystream.org/#/proposals/197
+
+### How to submit a report
+
+- Storage Lead should create a PR on Joystream/community-repo repository. 
+- Create text proposal for approve by the council
+- Once the proposal is approved and PR merged - put a message on the forum, including links to the PR and proposal

rules/WG_Lead_Term_Limits.md

@@ -0,0 +1,24 @@
+# WG Lead Term Limits
+
+*Based on the KPIs https://blog.joystream.org/sumer-kpis/#10.11*
+
+*Pre-proposal Discussion https://testnet.joystream.org/#/forum/threads/372*
+
+### For current Leads the soft term limit (starting from when this proposal is approved) is 1 month.
+
+The process once 1 month has been reached:
+1. The council secretary or deputy will create an `opening` for a new lead position, to see who is interested in doing the role. A proposal will then be created to begin review of applicants 1 week after.
+2. Once the review period starts, any user with enough tokens can create a proposal to fire the current lead and/or hire a new lead. Note: the current lead must be fired if a new lead is to be hired.
+3. Whatever proposals are made by the community (including by council members), the council can at this point vote on whether to fire the previous lead and hire a new lead, or to keep the previous lead in place.
+4. The current lead can also apply for the opening.
+5. Whatever the result of the new opening is, a new `opening` proposal will be made 1 month after, repeating the process.
+
+In the event the current lead is fired, they can stay on as: 
+- a guide (to help the newly hired lead on how to manage the position for a week). This will be paid at the previous rate + 50% for one week (via `spending proposal`)
+- also as a worker if they apply for an opening. The new lead is encouraged to hire the old lead as a worker if there are enough places, since the old lead will have desirable skills to help with the group.
+
+* In the event of a firing, the exact criteria for the transition period between the old and new lead will be discussed on the forum with the old lead and issued as a text proposal for approval by the council
+* In the event of a firing due to the soft term limit, it should not be considered that the lead was bad at the position, this is just a process to try and get a rotation of leads.
+
+### Exceptions
+* In the event the current lead is still in mid-process of implementing something important, they can create a text proposal with a description of what they're working on to allow for a one-time 2 week extension to their term before the `opening` proposal is created by the council secretary or deputy council secretary.