-
Notifications
You must be signed in to change notification settings - Fork 3
A: Yes, it will be always Open Source and there will be always free Versions!
A: We plan two commercial Versions. For 9 USD you can financially support us. If you want you can remove the "Powered by V²Configurator" URL. For 49 USD you can support us stronger and no longer have to release back your code changes to us.
A: There are many areas where you can help: Translations, Adding Functions, Create Examples. For more information → Contributor's Manual
A: We have a $1 US item in our online shop. You can select any amount. We feel $9 US is fair.
A: → GitHub►Issues►V²Configurator
A: Go ahead! It is under GPL v2 and commercial use is welcome. Please remember to release back to us any improvements you make. This will also reduce your work when installing a new and improved version from us, as your improvements will be in it already.
A: Yes. V²Configurator is maintained by the V² Open Source Movement and we plan to improve and maintain it for many years to come!
A: If you find a bug the best way is you fix it yourself, then send us a Pull Request, with a description how to reproduce and how your fixed it. For more information → Contributor's Manual. If you can't do that, please report the Bug → GitHub►Issues►V²Configurator
A: Our aim is to deliver fully functional configurations to the user of the configurator. There will be two scenarios: A) All parts are available in the online shop. In such case 3rd Party parts are not needed. B) Lets take our first Use Case as example. To build a working ViCase computer you need our ViCase Parts but also you need parts from third parts, such as motherboard and CPU. For the users convenience we have 2 shopping carts for the two shopping locations. As Admin you can disable the 3rd party shopping cart by simply not filling out 3rd party parts in the Json file.
Short A: Json delivers same benefits (for this project) at a much lighter footprint with increased compatibility and greatly reduced learning curve for the admin.
Long A: Everything would be more heavy when using MySQL. The server requirements would be higher. E.g. we no longer could host the Demo on GitHub Pages. The development process would be much more heavy. Because we can host the Demo on GitHub Pages, we have an integrated test environment with GitHub. This makes it so much easier for casual contributors! Last but not least not everybody is familiar with MySQL. Instead using Json is very simple. And thanks to the Json Form Editor the comfort of working on your data is actually the same.