Note: this is a discussion daft of the grant program, subject to approval of the Magma Core Foundation Governing Board.
Please create an issue in the grant repo and use this submission template for an easier submission build out
Project Name
This is your opportunity to convince the community of the impact and importance of your ask. This should be a brief description of the project that captures both the value and deliverable in a few sentences (or a tweet) and why it's needed or matters.
This is the amount you're requesting for the grant, not necessarily the total budget.
Each proposal submitted must have a sponsoring Codeowner (as defined in the Magma Technical Charter).
Please provide your legal name and a link to the submitted issue to [email protected]. This will streamline the contract process and KYC. A lack of this information will delay the contract.
Team or Project website: (optional)
Team or projects social: (optional)
Code Repos of team or key applicants:
(In lieu of public repos, please list a short bio of the applicants.)
https://github.com/organization
https://github.com/team-member-0
https://github.com/team-member-1
https://github.com/team-member-2
We expect a clearly articulated final deliverable for the project.
If the project utilizes legacy or other codebases, please specify this and link to applicable repos. In addition list any specific IP licenses you are utilizing.
Where relevant, please include mockups/designs of any UI/hardware components, and API specifications of the core functionality.
It is often helpful to include an overview of the tech stack to be used, including any required dependencies. Documentation of core components, protocols, architecture or schematics to be deployed within or as the MVP is even better.
This section should break out the development roadmap into a number of milestones.
Since the milestones will appear in the grant contract, it helps to describe the expected functionality and how it can be validated.
Whenever milestones are delivered, we refer to the contract to ensure that everything has been delivered. The level of detail must be enough to later verify that the project meets the specification.
MS/Roadmap EXAMPLE:
| Milestone + Date | Deliverable Summary | Cost |
|---|---|---|
| MS1, Date | Complete project proposal & design doc consistant with Magma's contribution process, reviewed and accepted by Magma TSC | 5,000 USD |
| MS2, Date | Capability xxx capability, with Unit tests, submitted as pull request and reviewed by Magma Codeowner | 2,500 USD |
| MS3, Date | Capability xxx capability, with Unit tests, submitted as pull request and reviewed by Magma Codeowner | 2,500 USD |
| MS4, Date | Capability xxx capability, with Unit tests, submitted as pull request and reviewed by Magma Codeowner | 2,500 USD |
| MS5, Date | Capability xxx capability, with Unit tests, submitted as pull request and reviewed by Magma Codeowner | 2,500 USD |
| MS3, Date | MVP of completed feature, ready for integratin tests and release | 10,000 USD |