diff --git a/applications/ticketing-events-nft-platform b/applications/ticketing-events-nft-platform deleted file mode 100644 index b40a0e27..00000000 --- a/applications/ticketing-events-nft-platform +++ /dev/null @@ -1,168 +0,0 @@ -# Mintbase Grant Proposal - -> This document will be part of the terms and conditions of your agreement and therefore needs to contain all the required information about the project. Don't remove any of the mandatory parts presented in bold letters or as headlines. Blockquote sections starting with a `>` (such as this one) can be removed. -> -> See the [Grants Program Process](https://github.com/Mintbase/Grants-Program/#pencil-process) on how to submit a proposal. - -- **Project Name:** Name of your project (e.g. DuoSwap Module) -- **Team Name:** Legal name of your team (e.g. Duo) -- **Payment Address:** A NEAR account to where funds can be transfered (e.g. myproject.near) -- **[Level](../README.md#level_slider-levels):** 1, 2 or 3 - -> ⚠️ *The combination of your GitHub account submitting the application and the payment address above will be your unique identifier during the program. Please keep them safe.* - -## Project Overview :page_facing_up: - -If this application is in response to an RFP, please indicate this on the first line of this section. - -If this is an application for a follow-up grant (the continuation of an earlier, successful Mintbase grant), please provide name and/or pull request of said grant on the first line of this section. - -### Overview - -Please provide the following: - -- If the name of your project is not descriptive, a tag line (one sentence summary). -- A brief description of your project. -- An indication of how your project relates to / integrates into the Mintbase / NEAR ecosystem. -- An indication of why your team is interested in creating this project. - -### Project Details - -We expect the teams to already have a solid idea about your project's expected final state. Therefore, we ask the teams to submit (where relevant): - -- Mockups/designs of any UI components -- Data models / API specifications of the core functionality -- An overview of the technology stack to be used -- Documentation of core components, protocols, architecture, etc. to be deployed -- PoC/MVP or other relevant prior work or research on the topic -- What your project is _not_ or will _not_ provide or implement - - This is a place for you to manage expectations and to clarify any limitations that might not be obvious - -### Ecosystem Fit - -Help us locate your project in the Mintbase landscape and what problems it tries to solve by answering each of these questions: - -- Where and how does your project fit into the ecosystem? -- Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? -- What need(s) does your project meet? -- Are there any other projects similar to yours in the Mintbase / NEAR ecosystem? - - If so, how is your project different? - - If not, are there similar projects in related ecosystems? - -## Team :busts_in_silhouette: - -### Team members - -- Name of team leader -- Names of team members - -### Contact - -- **Contact Name:** Full name of the contact person in your team -- **Contact Email:** Contact email (e.g. john@duo.com) -- **Website:** - -### Legal Structure - -- **Registered Address:** Address of your registered legal entity, if available. Please keep it in a single line. (e.g. High Street 1, London LK1 234, UK) -- **Registered Legal Entity:** Name of your registered legal entity, if available. (e.g. Duo Ltd.) - -### Team's experience - -Please describe the team's relevant experience. If your project involves development work, we would appreciate it if you singled out a few interesting projects or contributions made by team members in the past. For research-related grants, references to past publications and projects in a related domain are helpful. - -If anyone on your team has applied for a grant at the Mintbase previously, please list the name of the project and legal entity here. - -### Team Code Repos - -- https://github.com/ -- https://github.com// -- https://github.com// - -Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine. - -- https://github.com/ -- https://github.com/ - -### Team LinkedIn Profiles (if available) - -- https://www.linkedin.com/ -- https://www.linkedin.com/ - -## Development Status :open_book: - -If you've already started implementing your project or it is part of a larger repository, please provide a link and a description of the code here. In any case, please provide some documentation on the research and other work you have conducted before applying. This could be: - -- links to improvement proposals or [RFPs](https://github.com/mintbase/Grants-Program/tree/master/rfp-proposal) (requests for proposal), -- academic publications relevant to the problem, -- links to your research diary, blog posts, articles, forum discussions or open GitHub issues, -- references to conversations you might have had related to this project with anyone from the Mintbase Foundation, -- previous interface iterations, such as mock-ups and wireframes. - -## Development Roadmap :nut_and_bolt: - -This section should break the development roadmap down into milestones and deliverables. To assist you in defining it, we have created a document with examples for some grant categories [here](../docs/grant_guidelines_per_category.md). Since these will be part of the agreement, it helps to describe _the functionality we should expect in as much detail as possible_, plus how we can verify and test that functionality. Whenever milestones are delivered, we refer to this document to ensure that everything has been delivered as expected. - -Below we provide an **example roadmap**. In the descriptions, it should be clear how your project is related to Mintbase. We _recommend_ that teams structure their roadmap as 1 milestone ≈ 1 month. - -For each milestone, - -- make sure to include a specification of your software. _Treat it as a contract_; the level of detail must be enough to later verify that the software meets the specification. -- include the amount of funding requested _per milestone_. -- include documentation (tutorials, API specifications, architecture diagrams, whatever is appropriate) in each milestone. This ensures that the code can be widely used by the community. -- provide a test suite, comprising unit and integration tests, along with a guide on how to set up and run them. -- commit to providing Dockerfiles for the delivery of your project. -- indicate milestone duration as well as number of full-time employees working on each milestone. -- **Deliverables 0a-0d are mandatory for all milestones**, and deliverable 0e at least for the last one. If you do not intend to deliver one of these, please state a reason in its specification (e.g. Milestone X is research oriented and as such there is no code to test). - -> :zap: If any of your deliverables is based on somebody else's work, make sure you work and publish _under the terms of the license_ of the respective project and that you **highlight this fact in your milestone documentation** and in the source code if applicable! **Teams that submit others' work without attributing it will be immediately terminated.** - -### Overview - -- **Total Estimated Duration:** Duration of the whole project (e.g. 2 months) -- **Full-Time Equivalent (FTE):** Average number of full-time employees working on the project throughout its duration (see [Wikipedia](https://en.wikipedia.org/wiki/Full-time_equivalent), e.g. 2 FTE) -- **Total Costs:** Requested amount in USD for the whole project (e.g. 12,000 USD). Note that the acceptance criteria and additional benefits vary depending on the [level](../README.md#level_slider-levels) of funding requested. This and the costs for each milestone need to be provided in USD; if the grant is paid out in Bitcoin, the amount will be calculated according to the exchange rate at the time of payment. - -### Milestone 1 Example — Implement Mintbase Modules - -- **Estimated duration:** 1 month -- **FTE:** 2 -- **Costs:** 8,000 USD - -| Number | Deliverable | Specification | -| -----: | ----------- | ------------- | -| 0a. | License | Apache 2.0 / GPLv3 / MIT / Unlicense | -| 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can (for example) spin up one of our Mintbase nodes and send test transactions, which will show how the new functionality works. | -| 0c. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | -| 0d. | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | -| 0e. | Article | We will publish an **article**/workshop that explains [...] (what was done/achieved as part of the grant). (Content, language and medium should reflect your target audience described above.) -| 1. | Mintbase module: X | We will create a Mintbase / NEAR module that will... (Please list the functionality that will be implemented for the first milestone) | -| 2. | Mintbase module: Y | We will create a Mintbase / NEAR module that will... | -| 3. | Mintbase module: Z | We will create a Mintbase / NEAR module that will... | -| 4. | NEAR chain integration | Modules X, Y & Z of our custom chain will interact in such a way... (Please describe the deliverable here as detailed as possible) | - - -### Milestone 2 Example — Additional features - -- **Estimated Duration:** 1 month -- **FTE:** 1 -- **Costs:** 4,000 USD - -... -## Future Plans - -Please include here - -- how you intend to use, enhance, promote and support your project in the short term, and -- the team's long-term plans and intentions in relation to it. - - -## Additional Information :heavy_plus_sign: - -**How did you hear about the Grants Program?** Mintbase Website / Medium / Twitter / Element / Announcement by another team / personal recommendation / etc. - -Here you can also add any additional information that you think is relevant to this application but isn't part of it already, such as: - -- Work you have already done. -- If there are any other teams who have already contributed (financially) to the project. -- Previous grants you may have applied for. diff --git a/applications/woocommerce.md b/applications/woocommerce.md new file mode 100644 index 00000000..6207ad1e --- /dev/null +++ b/applications/woocommerce.md @@ -0,0 +1,147 @@ +# Mintbase Grant Proposal + + +- **Woocommerce Marketplace:** +- **web3devs:** Legal name of your team (e.g. Duo) +- **0xe83f27e5b26FbDa7F4ec8bA25139ef249d1cE3f0:** We would like to ask for a stablecoin please here is our USDC addy +- **[3]** +> ⚠️ *The combination of your GitHub account submitting the application and the payment address above will be your unique identifier during the program. Please keep them safe.* + +## Project Overview :page_facing_up: + +If this application is in response to an RFP, please indicate this on the first line of this section. + +If this is an application for a follow-up grant (the continuation of an earlier, successful Mintbase grant), please provide name and/or pull request of said grant on the first line of this section. + +### Overview + +Please provide the following: + +We would like to add to the ability for a NFT project owner that already knows how to use WordPress with WooCommerce to use MintBase as the underlying technology to launch their NFT project, +maintain their own marketplace and use these NFT as a gating to other sections of the site. +We are interested in doing this because we have already created the NFT gating NEAR plugin. We feel that artists would also like to maintain everything in an enviroment they already know. + +### Project Details + +We expect the teams to already have a solid idea about your project's expected final state. Therefore, we ask the teams to submit (where relevant): + +We would create a flow between how creating a ecommerce marketplace within Woocommerce works today with integration within MintBase APIs. +Based on this flow we would create wireframes needed to pass on the to the geeks to start implmentation of the front/back end. + + +We would be using as much of the native WP stack as possible with GoLang/Rust as a backup for anything WP cannot handle natively. Meaning if we need a middle ware component between WP and MintBase our goto would be Golang/Rust. + +We see a simular plugin being used with Ethereum but the flow is not super easy. We would take this same concept but also use feedback from the artists on how to better the flow. + + +### Ecosystem Fit + +Help us locate your project in the Mintbase landscape and what problems it tries to solve by answering each of these questions: + +We love how Mintbase is concentrating on the ease of use. We feel taking this same methodology but putting it to the #1 used CMS by artist would be an ecosystem match. +If we do this correctly the Artist would not need to hire a geek to help them create their NFT projects inside their already used website. There would not be any redirects or two system accounting issues. + + +## Team :busts_in_silhouette: + +### Team members + +We are a team of 7 geeks at https://web3devs.com + +### Contact + +- **James Ruffer:** Full name of the contact person in your team +- **james at web3devs dot com:** Contact email (e.g. john@duo.com) +- **https://web3devs.com:** + +### Legal Structure + +Happy to provide this in private so trolls stay away. +However we are a legal Delaware LLC + +### Team's experience + +We have been around for a bit. Feel free to see all our projects on our website. We did just deliver a grant from NEAR called accessbynft.com . + +### Team Code Repos + +- https://github.com/web3devs + + +Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine. + + +### Team LinkedIn Profiles (if available) + +- https://www.linkedin.com/in/jamesruffer + +## Development Status :open_book: + +If you've already started implementing your project or it is part of a larger repository, please provide a link and a description of the code here. In any case, please provide some documentation on the research and other work you have conducted before applying. This could be: +We have a ton of things on our website and github. + + +## Development Roadmap :nut_and_bolt: + + +### Overview + +- **90 days:** +- **4 Full-Time Equivalent (FTE):** Average number of full-time employees working on the project throughout its duration (see [Wikipedia](https://en.wikipedia.org/wiki/Full-time_equivalent), e.g. 2 FTE) +- **81,000 USD:** Requested amount in USD for the whole project (e.g. 12,000 USD). Note that the acceptance criteria and additional benefits vary depending on the [level](../README.md#level_slider-levels) of funding requested. This and the costs for each milestone need to be provided in USD; if the grant is paid out in Bitcoin, the amount will be calculated according to the exchange rate at the time of payment. + +### Milestone 1 - Setup Testing enviroment with design and dev teams. + +- **Estimated duration:** 20 days +- **FTE:** 4 +- **Costs:** 27,000 USD + +| Number | Deliverable | Specification | +| -----: | ----------- | ------------- | +| a. | License | Apache 2.0 / GPLv3 / MIT / Unlicense | +| b. | Documentation | We will provide the Miro flow, figma wireframes as well as the Asana board for this projects next 90 days. | +| c. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | +| d. | Testnet | We will provide a live testnet MVP for Woocommerce that can be used to test all the functionality delivered with this milestone. | + + +### Milestone 2 — Core Developement + +- **Estimated Duration:** 1 month +- **FTE:** 4 +- **Costs:** 27,000 USD + +| Number | Deliverable | Specification | +| -----: | ----------- | ------------- | +| a. | Backend | We will start maping the WooCommerce add product features to the Mintbase APIs | +| b. | Backend | We will implement the minting and display of meta data pushed to the WooCommerce native marketplace with status on each mint. | +| c. | Backend | Allow WP admin to edit and push NFT marketplace information to end users. | +| d. | Frontend| We will allow the WooCommerce native frontend to work with the mapping of the information of the Mintbase backend. | + +### Milestone 3 — Reporting, Beta testing + +- **Estimated Duration:** 1 month +- **FTE:** 4 +- **Costs:** 27,000 USD + +| Number | Deliverable | Specification | +| -----: | ----------- | ------------- | +| a. | Backend | We allow WooCommerce to add/delete/report product features natively in its dashboard. | +| b. | Backend | We will allow accounting xls downloading. | +| c. | Beta Testing | Allow WP admin and WP uusers to use the marketplace. | +| d. | Bugs| We will Address and Fix bugs. | + +## Future Plans + +Please include here + +We will setup a beta site for Artist to use and educate themselves on the how tos. +We will update the general plugin and WP updates for 3 months as part of this grant. + + +## Additional Information :heavy_plus_sign: + +**How did you hear about the Grants Program?** Mintbase Website / Medium / Twitter / Element / Announcement by another team / personal recommendation / etc. + +Here you can also add any additional information that you think is relevant to this application but isn't part of it already, such as: +We have already had a plugin approved with the official WP Marketplace for NFT gating. We feel this is the next step on helping Artists get thier projects posted without being a geek like us. +