Improving spending_proposal_categories.csv

[mochet]

Current Process & Problems

We monitor new spending proposal and add them to this file: https://github.com/Joystream/community-repo/blob/master/governance/spending_proposal_categories.csv
Only spending proposals are tracked and this is a manual process.

Solution

A script needs to be created that can fill in the values from all proposals and output them in a CSV format that is compatible with the preexisting CSV.
This new script should include the following information:

• Proposal number (this should start at 1)
• Author name
• Proposal Title
• Proposal Type
• Proposal Description (not 100% sure about whether this is worth including or not)
• Proposal outcome (Executed, ExecutionFailed, Rejected, Slashed, Withdrawn etc)
• Proposal amount (this includes both spending proposals + mint proposals)
• Actual spending from spending proposal (if a proposal asks for 5m tJOY and is not approved, it has not actually spent 5m)--in this case this amount would be 0
• If a spending proposal--what was the recipient address. (and member name as a separate field)
• Blockheight submitted
• Blockheight executed/failed/expired/withdrawn)
• DD/MM/YYYY HH:MM proposal was submitted using GMT (this should be in a format that Google Sheets can interpret as a time code
• If the proposal is expired or withdrawn -- how much stake was burned?
• Number of approve/abstain/reject/slash votes for each proposal (it is unclear if this information would be that easy to get)
• Maybe also which council term the proposal was created in and which one it was executed within.
• The voting period (i.e. for a text proposal this is 72000 blocks
• If at all possible--the exchange rate at the time of submission (this one might be too complex to deal with?)

ALTERNATIVE: make the script output a JSON on joystreamstats and run the script every 6-12 hours. This is the more preferable option as it means that the person maintaining the categories of proposals (myself) does not need to maintain a node.

Reason/Purpose

There is currently no way on the Joystream Leaderboard to generate data from proposals, we have a limited amount of information available from tokenomic and council reports, but this doesn't go deep enough into things to see the big picture.

[mochet]

This is now intended to be implemented into the Joystreamstats API (https://api.joystreamstats.live/) therefore the CSV requirement is no longer relevant.