Treasury proposal: SubBooster, an open source remote compiling tool for Substrate developers.

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

Project short description:

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.

How to benefit our community?

• It helps to save much time for Substrate developers, boost their project and lower the threshold for new comers to Substrate dev community.
• It will create more use cases for important features such as onchain identify/vote to improve the value of Kusama/Polkadot network
• We are expecting 200 common users after milestone1, and 500 users after milestone2 along with acceptable user experience.

Technical roadmap

• Milestone 1: backend service automation and onchain integration;(2 months)
• Milestone 2: Feature complete and user onboarding;(2 months)
• Post Milestone 2: Regular server health check and monitor; (2 months)

Milestone 1: backend service automation and onchain integration.(2 months)

Tasks:

• scripts to deploy and manage the compiling server;
• a web service can save the information provided by the user;
• a scheduled task to register new user in compiling server;
• detail documentation on how to use this compiling service;
• start onboarding users manually to 100 users.
• Kusama/Polkadot onchain identity integration;
• Integrate polkadot js extension to sign message;
• Backend service verify the message and apply user to compiling server;
• Automatically onboarding 200 users;

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.

Milestone 2: Feature complete and user onboarding

Tasks:

• benchmark how many users can be supported in single server;
• scripts to scale up compiling servers;
• add promote code logic for students and new comers;
• implement cancellation of service based on the above mentioned rules;
• consulting 3rd party to finalize terms of service.
• Tech support.

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.

Post Milestone 2: Regular server health check and monitor

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.

Treasury request:

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)

Info and contact

Kevin: [email protected]

Popeye: [email protected]

Github: https://github.com/sub-box/sub-box