4 ms·
There is also a free (as in beer) license: https://slint-ui.com/ambassador-program.html https://slint-ui.com/ambassador-program.html That should cover your need
by ogoffart 5y ago
There is also a free (as in beer) license: https://slint-ui.com/ambassador-program.html https://slint-ui.com/ambassador-program.html That should cover your need for your hobby project.
For your OSS work, you can license your code in MIT, BSD, Apache, or any license compatible with the GPL3, as long as the combined product is GPL
- salmo 5y agoI can’t choose an option where the terms may change in the future. And that “combined software has to be GPL” isn’t OK with me. I’m just not happy with the GPL from a legal and philosophical stance. Totally recognize I’m weird and pedantic there. But yeah, not wanting to debate my personal choices, more speaking to how the licensing decisions may impact the business success. Making money w/ an open source product or really any library these days as your business’s product is hard. It’s hard to sell, commercially “extend”, or sell professional services around. I don’t envy the situation. It’s hard enough for RedisLabs, MongoDB, etc. who have more opportunities there.