Notice: Polkadot has migrated to AssetHub. Balances, data, referenda, and other on-chain activity has moved to AssetHub.Learn more
"Standard" guidelines to submit a proposal for the Kusama Treasury
While we all agree a strictly-structured proposal could sometimes be detrimental to the idea behind a submission, and I am not suggesting we should limit the proposals' explanation to **ONLY **certain points, I think we should all agree on a **list of elements to be included to better-assess the quality of a submission. **
I have drafted a first copy for a submission skeleton that can be used as a template to follow (and complete with more elements) for any proposal to be submitted to the Kusama Treasury:
https://docs.google.com/document/d/14E019tobfgoQTGgX4LRnbh7grOlD8yQsfqWuAgrsJMw/edit?usp=sharing
New ideas, edits and comments on this are welcome! Feel free to use the template as well.
Comments (5)
Good structure. You may want to see credentials of the team behind the proposal. Optionally, since so many teams are building so many things, you may want to see some evidence of research in that, just to make sure people do their homework before applying that they are not duplicating efforts and/or to encourage re-use.
I agree that it’s good to have some kind of recommendation (not obligatory) template that helps people understand which topics are of interest to the council when considering funding proposals from the treasury.
@RTTI-5220, your template looks great. But I would also suggest to add a separate item on the presentation of the team that will work on the task described by the proposal.