As you may know, we proposed dotreasury and finished our work for M1. Check post 352 for the proposal discussions and here for our M1 report. We hope you like our work and now we are proposing the dotreasury M2.
It will be similar with account system of polkassembly.
It's common that one project have support from several proposals. So it's not enough to just comment on one proposal or tip. We should get to know the funded projects and comment them from a higher view.
In the detail page, there will be descriptions about:
Some consultant work maybe involved for this. I may ask questions to some beneficiaries and councilors.
Mainly in the expense detail pages and project detail pages. Remarks may come from:
Only burnt records list, no need to show the detail.
We will show it like 20% from gas, 30% from slash, etc. Maybe a doughnut chart will be shown.
Mainly solve problems we mentioned in our M1 report.
Cost for M1 can be checked here, and the time is a little tight for us.
Considering our experience of M1 and the upcoming China spring festival, we want to decide the time to be 1.25 months. 3 developers, 1 designer and 1 operation intern will work on this M2, but we will not request cost for the operation intern.
So the cost list will be:
Take KSM price as $70, so the KSM expense: ($29375 + $800 + $500) / $70 = 438KSM
Output:
What's your next plans?
You can see our rough milestones here. Though there maybe small changes, our final target is to introduce retrospect mechanism to current treasury workflow. In the future, we aim to build a reputation system for treasury participators. Of course, we will do it cautiously.
What's your plan to integrate polkadot?
Our plan is after M2.
Some other possible questions can still be seen here.
We are OpenSquare team, dedicated to facilitate the collaboration between projects and developers.
Dotreasury M2 is a proposal to continue the development of the doreasury platform. The main goals for M2 are:
The estimated time for M2 is 1.25 months with a cost of 438 KSM. The funds will be used for developers, a designer, server fees, and a cloud MongoDB for stable deployment. The final output will be new features on doreasury.com and updates to the code repository. The team's next plan is to introduce a retrospect mechanism to the treasury workflow and build a reputation system for treasury participators. Integration with Polkadot is planned after M2.