🌟 Future Direction for this project #161
Description
Original Scope and Direction
Originally this project was started as a tool to serve the Intersect Constitutional Council.
See first issue #1
By allowing Intersect council members to inspect, validate and sign vote transactions.
We aimed to be able to enrol council members as true key holders within the Intersect key hierarchy.
Future Direction
With elections for Constitutional Committee in on-going currently, the Intersect Constitutional Council is not running again. Making the Intersect specific aspects of this project obsolete, following the election of a new Constitutional Committee.
Furthermore with the elections, there will likely be election of new community councils. With the current budget scopes there is little to no support allocated for Constitutional committee tooling to support these councils.
Intersect is committed to foster on-chain governance, this includes supporting these new community councils with tooling. Thus it makes sense to adapt the work here to suit this pending new landscape of community lead Constitutional Committee members.
Proposed Scope
Make Generic
Remove elements specific for the Intersect council.
Ensure the app is better suited to be used by all Constitutional Committee members.
Wider Feature Set
Expand feature set to better suit all Constitutional Committee members.
(we can take inspiration from other CC tooling from CF see here)
Ideas:
- Supporting creation of vote rationale files
- reuse work from Thomas
- Build vote transactions
- Show live governance actions - what has the user voted on prior
To achieve these we will need to change the app to be multi-page;
- Page to inspect vote transactions (what we have now)
- Page to generate / validate vote rationales
- Page for on-chain governance action data
Next Steps
- Close out any active branches and issues being worked on
- Socialise new direction and get feedback from stakeholders
- Create issues for new direction