Treasury proposal: SubBooster, an open source remote compiling tool for Substrate developers.
EXPLANATION: Previously we were thinking about submit a treasury spending proposal for each milestone. But we made a mistake when submitting the proposal that the spending is the sum of milestone1 and milestone2. It seems the only way we can do is to submit both milestones in this proposal. We're sorry for the inconvenience.
We've been working on this project for a few months, from an early idea to a functional MVP (https://github.com/sub-box/SubBox), which could now deliver a pretty good experience. We expect to add more automatic features and Kusama/Polkadot integration with the founding from treasury. By the way, it is really cool to compile a Substrate based project within 4.5 minutes.
We really want to gain your understanding and support to help us complete the project!
The original and detail discussion post:https://kusama.polkassembly.io/post/335
We are introducing an open source remote compiling speed up tool which is named SubBooster to Kusama and Polkadot community.
By using the remote compiling service, developers and learners within the eco could compile their projects in a more efficient way that enable them to do it within 4.5 minutes.
We also integrate some other functions like onchain identity to this service to create more use cases for the network.
Tasks:
After the 1st month, early users should be able to submit a form with user and public key information and enjoy the compiling service within 10 mins, without manual operation;
After the 2nd month, users can register the web app with Kusama/Polkadot account and sign a message to prove that they are eligible to use the compiling service.
Tasks:
After this milestone, users should be able to apply and cancel free compiling service based on their onchain identity/vote. We also plan to help students who don't have enough ksm to register onchain identity.
Not only Substrate devs, we will also try to reach out Rust community, and provide guidance docs and online communication through Discord, Telegram, Wechat, etc. To ensure more people make best use of this tool.
When we've completed the milestone 1 and 2, we'll keep to provide service for another 2 more months. And after this 2 months, we will try to be keep it alive as a public infrastructure through another proposal with a minimal server cost.
We have 2 developers and 1 part time community manager devote to this project. According the task in the technical map, we've made a [budget in detail.] (https://docs.google.com/spreadsheets/d/1ckMMUDzGKf7QGjv3sKBmHGN6daNktb_KhJgA6Ozf0uU/edit?usp=sharing)