Comment by jasonlotito
2 years ago
I was going to come here and post about how this is exactly what I've been looking for, but then I read this.
So, my kneejerk reaction to this deceptive use of open source is to just say "no" and move on. However, I read through your philosphy, and I have a question.
> considering the substantial R&D resources required for the application layer, we believe that businesses and networks utilizing our software for commercial purposes should contribute towards its ongoing development, allowing maintainers to support and enhance the platform.
That seems to be the crux of the concern here. I can respect that. So, why do existing open source licenses not suit you? For example, you could release the software under the AGPL, and still dual-license it as you wish.
Rather than assume bad faith, I'm going to give you the chance to correct yourself. At the very least, calling yourself open source at the moment is deceptive, whether you realize it or not.
The most of are repost are open-sourced with MIT licence. It's clear now, that the way we put words together in the license for clients is not clear. Our idea is straightforward: if you want to use the software, you can do so for free, whether for personal use or within an organization. However, if you aim to sell it for profit(like change the logo and put price tag on it), you need to contribute to its creation in some way; this is why permission is required. At least, that's the case at this early stage.
I don't see the problem with using Anytype License instead of AGPL. AGPL allows commercial use as long as the source code is provided, while Anytype disallows commercial use. Other than that it is the same, and is "open source" regardless. As in, OSI doesn't trademark "open source".