Conversation
The commons license that you link here, does **NOT** do what you say it does. You can distribute a software, and also share executables, that are licensed under the commons clause: > Commons Clause only forbids you from “selling” the Commons Clause software itself. You may develop on top of Commons Clause licensed software (adding applications, tools, utilities or plug-ins) and you may embed and redistribute Commons Clause software in a larger product, and you may distribute and even “sell” (which includes offering as a commercial SaaS service) your product. You may even provide consulting services (see clarifying discussion here). You just can’t sell a product that consists in substance of the Commons Clause software and does not add value. Signed-off-by: ShalokShalom <shalokshalom@protonmail.ch>
|
Yeah honestly, the current license was supposed to be a placeholder for a custom one written by a lawyer. I had it all planned, but then I got into a bad state in my life and couldn't afford to spend money on it anymore… thank you for the PR, I'll look into it |
If you want a completely new license, that is not only costly, it is also prohibitive since people tend to avoid software that is written in it. You seem to be very concerned about someone else selling the app, and I think the Common Clause license is actually a good license for you. Another solution could be the 'Functional Source License' It also prevents selling, and converts into an open source license automatically after 2 years. Much success |
2 participants
The commons license that you link here, does NOT do what you say it does.
You can distribute a software, and also share executables, that are licensed under the commons clause: