3 ms·
I prefer the model of making it properly free and opensource, but charging money for precompiled binaries and a support contract. I'd add a simple startup bann
by londons_explore 4y ago
I prefer the model of making it properly free and opensource, but charging money for precompiled binaries and a support contract.
I'd add a simple startup banner saying "This program is UNSUPPORTED by @rui314. For a paid supported version, contact foo@bar.com".
The paid support would entitle one access to a forum of other paid support users, where bugs and feature requests can be posted and rui might prioritize them over regular bugs.
- londons_explore 4y agoSimple approach: Set up a page saying that support costs a quarter hour of engineering average salary for the country/year/employee who uses Mold. Eg. in a company in the USA, with 30 in the engineering department, that would be $600/yr. Let them know that the license continues to be valid if the company grows during the year. When a company pays for a license, you give them a license code like "2023-06-Vmware-7676". Tell them to put that code into ~/.mold/license, or to set the env var MOLDLICENSE= to that. The same code lets them into a discussion forum. When the linker starts, it prints a string saying "Mold Linker, Licensed to Vmware. Support license expires June 2023. See https://github.com/rui314/mold/wiki/support https://github.com/rui314/mold/wiki/support for details". If there is no license, or the license is expired, it prints "This program is UNSUPPORTED by @rui314. For a paid supported version, see https://github.com/rui314/mold/wiki/support https://github.com/rui314/mold/wiki/support". But obviously it still works just fine, license or no license.