Skip to content

Latest commit

 

History

History
82 lines (53 loc) · 4.42 KB

Performance_of_Storage_Lead_4-Nexusfallout.md

File metadata and controls

82 lines (53 loc) · 4.42 KB

Performance of Storage Lead 4-Nexusfallout

Provided Reports

Links File on Github Proposal Pull Request Date Note
Report 5 - - - 27 June 2021 On-chain forum
Report 6 report-6.md Proposal 234 PR 221 04 July 2021 Merged and approved
Report 7 report-7.md Proposal 257 PR 230 11 July 2021 Merged and approved
Report 8 report-8.md Proposal 294 PR 243 18 July 2021 Merged and approved
Report 9 report-9.md Proposal 320 PR 260 25 July 2021 Merged and approved

Summary

Storage Lead 4-Nexusfallout

Note

  1. All reports have been approved by council via text proposal
  2. According to Reporting Requirements Nexusfallout must submit weekly reports to the community-repo repository via Pull Request. Done.
  3. Report 5 not provided on Github
  1. Frequency - 1 week. Done
  2. Put reports to the Community-repo repository. Done. Folder here
  3. Create text proposal for approve by the council. Done
  4. A full breakdown of system specs for each storage provider - Started doing with report 9
  5. Bandwidth use on each provider - not provided
  6. Periodic upload tests - Made but by @tomato's and @l1dev's hands. Not provided in reports
  7. Helios Output - Done
  8. Free space of each one of the storage workers - Done
  9. Set reawards for Storage Providers - Done

Compare with Helpdesk

  • Storage Lead
  1. Available on Discord - Done
  2. Hire/fire/warn storage workers - Done
  3. Manage Storage Workers - Done
  4. Set Vouchers Limits - Done. Submissions on Discord and here
  • Storage Workers
  1. All storage providers have installed nodes
  2. The update process is underway
  3. Once a week, Storage Providers provide df -h
  4. Do ipfs stats repo by request
  5. Do ipfs config Datastore.StorageMax "XXXGB" by request

Performance for the Lead

  • At least 95% of the work he did

Performance for the Workers

Referring to the reports, it is impossible to understand how effective the Providers are. We still don't have tools for it. But our Stellar line-up @tomato, @nexusfallout, @freakstatic and @l1dev are trying to find the way every day

  • joystreamstats

  • julysake

  • 0x2bc

  • kalpakci

  • seainvestor

  • maxlevush

  • joyval

  • dapplooker

  • godshunter

Suggestion for the path forward

According to WG Lead Term Limits Lead's term soon ends.

4-Nexusfallout showed great efficiency. We would like to continue working with him. But more worthy candidates should try the role. The Council will decide the further fate of Storage Lead referring to the results of the applications.