Collectives is a polkadot parachain which host polkadot alliance business. Please check substrate alliance pallet here. Subsquare support following user stories:
Generally our work includes:
Estimated development time:
|Scan scripts||80||1 FTE * 2 weeks|
|Server RESTful apis||40||1 FTE * 1 week|
|Fronted||160||2 FTE * 2 weeks|
|Design||32||1 FTE * 4 days|
|Statescan support||56||1 FTE * 7 days|
An OpenGov spent proposals pie chart is implemented to show the ratios of treasury proposal spent by different OpenGov tracks. Jobs include:
|OpenGov spent proposals pie chart||48||2 FTE * 3 days|
|Proposal second multiplier||16||1 FTE * 2 days|
|Header search box||16||1 FTE * 2 days|
|Nested comments||32||1 FTE * 4 days|
|Close collective status and button||16||1 FTE * 2 days|
We have more than 260 democracy referenda on kusama, and more than 160 referenda on OpenGov. Though we show votes detail on each referendum detail page and simple summary data, more statistics will help us to analyze how governance models work. We plan to implement following governance statistics.
Please check this figma link for more design.
Currently on users' profile page, we can see various proposed proposals by the user. They are not enough to show all users' governance participation. The activities we'd plan to add including:
It's a problem that we usually forget which referendum we have voted, and it's troublesome to query them and remove them before we can transfer the locked balances. We propose to implement interfaces for user to manage the votes.
Many community members has expressed their positive comments about subsquare's UI&UX. We never stop our work for better design, and we propose to implement our new design which we believe will bring users better experiences. The new design has improvements in following aspects.
Please check here for the full design on figma.
|Governance statistics||640||4 FTE * 4 weeks|
|User goveranance participation||240||3 FTE * 2 weeks|
|Subsquare new design||240||3 FTE * 2 weeks|
|Other enhancement features||168||3 FTE * 7 days|
As dotreasury is becoming popular in dotsama governance users and several community members suggested us to add dark theme for better view at night. We propose to implement it in this proposal. Please check figma design for details.
We now have a total stack chart on home page with with we can roughly see the treasury spend trend. We propose to implement a chart to show treasury spend trend by periods which provides us another view to review the spend trend and details. We can also see spend details on each period.
Though dotrasury provide detailed treasury related data, sometimes it's troublesome for users to find out target data. We will provide a group of sort and filter functions to help users to locate target data more easily. Users will be able to:
|Dark mode||160||2 FTE * 2 weeks|
|Treasury spend statistic by periods||112||2 FTE * 7 days|
|More filters||48||2 FTE * 3 days|
Note: we'd explain that the dark mode estimated time is longer than that we estimated for subsquare dark mode implementation on proposal #155. The reason is the final time we spent on subsquare dark mode implementation is much more than the estimated(many details and corner cases). We won't request more fund for the not covered labor time, but hope get understanding for dotreasury dark mode estimation.
Please check above sections for details of each item. Taking hour rate $80, please check following budget list.
|Retroactive work||496||polkadot alliance support; dotreasury OpenGov spent pie chart; subsquare delivered enhancement features|
|Subsquare new features||1,288||Governance statistics; user governance participation view and management; new design and other enhancements|
|Dotreasury new features||320||dark mode; treasury spend statisc by periods|
|Total||2,104||Fiat cost: $168,320|
We want to leave more time for community and other potential implementers to review and give feedbacks. We may propose to implement it in next proposal.
Yes, we proposed referendum #164 on kusama for our maintenance work. Usually we separated our work into maintenance and new features development. The maintenance proposal, mainly including server cost and code base maintenance(refactor, bug fixes, UI tweaks, dependency upgrading, etc) is usually less controversial. We make new development plans based on our capacity and features evaluation which maybe more useful to the community. We may merge maintenance and new features proposal if our proposed new features always keep not so controversial.
We've started the development before submitting it on-chain, and we will update our progress with following table.
|Treasury spend statistic by periods||✅|
|Participated user filters||✅|
|OpenGov tracks comparation||✅|
|OpenGov each track and democracy referenda||✅|
|Each referendum data view enhancement: nested votes||✅|
|Each referendum data view enhancement: vote ratios between direct and delegation votes||✅|
|User votes activities||✅|
|User votes management||✅|
|OpenGov referenda preparing phase visualization enhancement.||✅|
|Support users placing OpenGov referendum decision deposit||✅|
|Allow users to mark any discussion/proposal post as a scam||✅|
|Democracy vote extrinsics.||✅|
|Support upload images direct with subsquare editors.||✅|
|The navigation menu will be a left sidebar style, always accessible.||✅|
|New detail page||✅|
|New profile page||✅|
Happy these excellent projects get the network's support.