-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
License? #1229
Comments
There are a couple of potential licenses in use on branches, but the |
I think the README is not updated when they removed the license file 164 days ago.
I'm hot a lawyer, but as far as I can remember, if a license is not mentioned, the default is "proprietary", hence your assumption is correct. Also I stumbled upon this article in opensource.org: Court affirms it's false advertising to claim software is Open Source when it’s not. So if we consider README as a legal document, then Memex is OSS, if we consider it as a wiki-like document with no legal implications, then it can be considered as "advertising" that Memex is MIT where in fact due to the lack of license it is proprietary. |
Also, Mozilla Addons page https://addons.mozilla.org/en-US/firefox/addon/worldbrain/ still says "MIT License" for the release 3.1.10 but as you said upstream has removed the license file long ago. It feels a bit disingenuous to not change/remove the license on Mozilla add-ons website. If not done by Memex devs then Mozilla should step in. |
It's not just license but upstream has also changed one of the core libraries ( Then how can this addon be listed as having "MIT License" on Mozilla Addons website when the addon can't even be built with the available code and needs at least one proprietary library to build? |
Memex devs have replied here that Memex is no longer intended to be open-source. |
The read me states the repo is under the MIT license, but the link is dead and there is no other license file. I just wanted to question/clarify the license this repo is currently under.
Cheers 🎉
The text was updated successfully, but these errors were encountered: