On top of that, the license itself is actually incredibly restrictive. I’m not a lawyer, but my read of the section on economic value seems very broad:
> does not include uses where the Software facilitates any transaction of economic value other than on Allowed Networks.
My read of “facilitates any transaction of economic value” means that I would be in violation if I used this to keep track of trading cards, made a grocery list, or tried to keep track of what I want to buy my friends for their birthdays. At least it would if I installed this on my home server and accessed it from the couch on mh phone.
If not, you should really talk to a lawyer first about this. Preferably one with knowledge of open source licensing. New software licenses are tricky and should be done by a lawyer and not by random HN comments. (Even if this is an overly well informed set of users on software).
As such, "most repos are open source" (from what I can see: MIT, some forked ones Apache 2.0) is nice, but the end product still isn't open source according to OSD.
There are people who value using "Open Source" for OSD-compliant licenses only (I tend to agree with that notion to keep things clear), but I didn't really want to discuss this: It's your project, after all, license as you wish.
I just wanted to provide a heads-up that the use of "open source" in the header here (and the front page on your site) doesn't match the expectations of a bunch of folks, so they know whether to look closer or not based on that.
I see how making the entire situation transparent muddies the message, but "Everything is Source Available, many parts are Open Source" would already clear things up a lot.
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.
See: https://www.gnu.org/philosophy/open-source-misses-the-point....
I don't blame you, it's a bit schadenfreude on my part because "open source" companies try to dress as free software but aren't
There are broadly two camps: Camp 1 who advocate for free software & free software alone, and Camp 2 who advocate for "open source" being an all-encompassing umbrella term for a few things, including free software. Those in Camp 1 are typically not supportive of the goals of those in Camp 2. Those in Camp 2 do often try and equivocate the two terms.
It really is the whole point of it, define more clearly what criteria must be fulfilled for software to be considered free software.
Is this a typo?
[0]: https://www.gnu.org/bulletins/bull1.txt
[1]: https://news.slashdot.org/comments.pl?sid=1129863&cid=268758...
5. No Discrimination Against Persons or Groups
6. No Discrimination Against Fields of Endeavor
Let's see https://opensource.org/definition-annotated/, _the_ definition for open source, specifically the sections titled "No Discrimination Against Persons or Groups" and "No Discrimination Against Fields of Endeavor":
"The license must not discriminate against any person or group of persons."
"The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research."
So what GP claimed seems to be exactly Open Source's point, no?
DaVinci Resolve is not source available. Anytype does not restrict you from forking the code as long as it is non-commercial. And it also lets you fork the code for commercial use, if you take their permission.
So it is simply a non-commercial open source license, with permission required for commercial use. Sure, not OSI Approved License™, but certainly "open source". If this was not "open source", neither would be GNU GPL, because it isn't permissive enough.
This is no different from Qt's dual license except that GPL allows commercial use too. Or, like Creative Commons NC licenses, but for software.
Open-Source is a generic term. It's the opposite of "closed-source".
The OSI is on the record on this: https://opensource.org/pressreleases/certified-open-source.p...
The only people who want to push the whole "The OSI's version of Free Software" defines "open-source" rather than "OSI Approved License™" are the Anti-Property GPL folks that never liked the term "open source" anyway, the trolls that want to force other people to work for free, and the people at the OSI
Any hacker news link?
This is a highly subjective take - it might be better to stick to objective dictionary definitions.
This project clearly isn't open source, & shouldn't be advertised as such, but on the other hand the intent here is a common/popular one these days, & its not the first of its kind: I'm surprised no-one has yet coined a term for this relatively new breed of "faux-pen source" or whatever it is.
Fwiw I do think it has it's place - it's certainly more than preferable to all rights reserved.