6 ms·
If you want to open all of your product's code, then you might want to use a public-private licensing model. https://indieopensource.com/public-private/users ht
by orlandohill 6y ago
If you want to open all of your product's code, then you might want to use a public-private licensing model.
https://indieopensource.com/public-private/users https://indieopensource.com/public-private/users
Have a look at the Parity Public License and the Prosperity Public License.
https://paritylicense.com/ https://paritylicense.com/
https://prosperitylicense.com/ https://prosperitylicense.com/
Those two licenses allow others to read, modify and redistribute your code. Parity requires that users open source their code, while Prosperity only allows non-commercial usage. If a potential customer doesn't want to be restricted by the public license you choose, they can instead buy a private license.
Also see License Zero's private license.
https://licensezero.com/licenses/private https://licensezero.com/licenses/private
- cercatrova 6y agoNote that the Prosperity, Parity and Licenze Zero licenses are not open source due to the restrictions they place on certain types of users, such as other businesses. This may be fine for one's usecase or as a business, but one must know that they are not in fact truly open source.
- andreareina 6y agoI’m not seeing where Parity discriminates against certain users, groups, or fields of endeavor. Clause 9 of the open source definition[1] seems a close thing, but the same reasoning for A/GPL applies. [1] https://opensource.org/osd-annotated https://opensource.org/osd-annotated