-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improving council reports #18
Comments
More additions:
|
One more metric we could add to council reports is to track the total potential council actions and what percentage of these are fulfilled during a council term. This would simply add up all the votes needed to reach quorum on the various proposal types (ex. a runtime needs 90% quorum, so on a 10 member council, this would be 9 required votes) The reason for this metric is it gives a very easy indication of how well the entire council performs. |
This PR adds the council report for round Joystream#18 (KPI 14.3)
…report Add sumer council #18 tokenomics report
Currently I complete all the council reports by hand and using small code snippets within the Javascript menu, there is a lot that could be improved and these could largely be automated and improved upon.
Compared to the tokenomics reports, the council reports should ideally focus on both:
You can look at the current set of council reports to get an understanding of what they show now: https://github.com/Joystream/community-repo/tree/master/council-reports
These improvements + automation could easily be completed for bounties, I can help to produce a template if necessary. The end product would ideally be a script which can take a start + end blockheight as input and output a detailed, useful council report that can then be completed with a bit of input for the opinion aspects.
The text was updated successfully, but these errors were encountered: