Council Secretary Workflow

[mochet]

This doesn't have a place on the community repo or forum just yet, but is a WIP so that this role is easier to do:

Council Secretary Workflow

This document serves as a basic workflow and overview of what the Council Secretary role involves. The council secretary is an informal role so unlike many other Joystream roles does not have fixed rewards or a fixed scope of work, so the workflow and responsibilities are heavily influenced by given KPIs and what happens during a particular council session.

Basic requirements & responsibilities:

• Communicate with CMs and users, create threads and make sure everyone is aware of work that needs to be done or proposals that need to be voted on
• Communicate with Jsgenesis, through proposals, forum and Telegram
• Keep a close eye on Github updates concerning the operations of the council, proposals and coming updates
• Help users to interact with the council and be aware of how proposals work
• Identify limitations or potential improvements for reports, elections, proposals and try to improve upon these
• Help push along the process of voting for proposals and elections
• Help to communicate processes and workflow in a transparent manner as much as possible
• Maintain a neutral stance as much as possible for everything

After new election is started:

1. Create thread for council applicants to post introductions in
2. Make people in Telegram aware and be helpful
3. Pay attention to application/vote/reveal stages and communicate any needs to the userbase
4. Make sure users are aware of potential benefits of participating in the council voting process
5. Make sure users are aware of the best way they can apply themselves when it comes to Jsgenesis votes

After new council elected:

1. Note the exchange rate at the start of council, produce figures corresponding to KPIs and dollar pool value
2. Create proposal to elect council secretary
   • Include Github link
3. Look through KPIs, produce forum thread breaking down each KPI and start discussion of each
   • Divide KPIs
     • Identify which require internal work
     • Identify which require external work (like KPIs that are dependent upon bounties)
     • Identify conditional KPIs (ex. a KPI which requires block production times, or a failure state for proposals being passed are conditional and not easily influenced by council)
4. Add threads for any new community KPIs and close old community KPI threads.
5. Regular checking on KPIs and making update posts in appropriate threads to ensure everyone is aware of what the current status of KPIs are
6. Add thread for council round feedback

After council ends:

1. Compile CM feedback from CM feedback thread
2. Produce council report

Other Tasks:

• Manage PRs on community repo
  • When approved by propposal or approved by ruleset, request review from Jsgenesis.
• Periodic user feedback capture
  • If required, help to create threads and mechanisms for user feedback.
• Periodic report generation
  • If required by KPIs, help to produce initial templates for reports and identify what important information needs to be shown at minimum.
• Periodic lead feedback
  • If required by KPIs, help to create threads, proposals and reports to capture user feedback on lead role performance,
• Rolling Github Community Repo proposals
  • Periodically collect outstanding PRs which have had no proposals made, and create a proposal listing them for the council.
  • Separate any problematic PRs and create separate proposals for them.
• Github Issues
  • Create and manage Github issues
  • Periodically create Github issues to try and capture feedback on improving reports
• Community KPI management
  • Help to make users of the platform aware of Community KPIs and be helpful on how to apply.