--- START OF LICENSE ---
Bare License:
Severability/salvatorius: If any word, part, portion, provision, of this is or should become illegal, invalid, null or void, rendering this unenforceable in any jurisdiction, then that shall not affect:
- The validity or enforceability in that jurisdiction of any other provision of this Contract Agreement; nor the validity or enforceability in any other types of jurisdictions on that or of any other provision of this Licensing Agreement.
- Nor any other character or part of the license/contract. In every & all cases, any part of the balence that could remain shall always continue to apply as a whole
(The rest of this license shall always remain in effect, as agreed, instead of completely being rendered/held as invalid or flawed by any judgement/form of law.)
(FOS)
<Year(s)> <Main Copyright Holder/Licensor(s)>
Everyone is permitted to redistribute verbatim (or modified) copies of this Contract Agreement/License Document & changing it is allowed.
The purpose of this Licensing option is to allow works to be available as Free & Open Sourced to the fullest extent that can possibly be permitted, which if the relevant works cannot be dedicated to the public domain with this license, then they shall still have the following fallback:
0.) Permission given to simply just do what you would want to, you are free to use the openly available work(s) however you may like & as you would see fit.
1.) Permission is also hereby granted, free of charge, for any person that is able to/can possibly obtain a copy of these works, code, and/or associated documentation files (i.e "Finished Product"), to deal in the work(s) as-is, without warranty. In addition, This could be for any purpose & is without restriction to the maximum theoretical extent, including but not limited to; the rights to use, copy, modify, merge, publish, distribute, sublicense/re-license/unlicense, and/or sell copies of the products, and to also permit persons to whom the end-work is furnished, to do so aswell.
- **This would include an explicit, perpetual, no-charge, royalty-free, & non-exclusive patent-license (along with any & all other relevant grants)
to make, have made, use, offer and/or sell, import, and/or otherwise transfer the relevant Work(s)
If there was ever to be a question regarding the terms or intention of this license, then the most open & permissive (or the user defending) opinion shall take precedence over any & all other options. This is because of the same reasons as stated before; the intention behind this license is to allow users to do what they would like & as they see fit, also to atleast have all the same rights that the Public Domain would provide. (Whether under local or international interpretations)
--- END OF LICENSE ---
- THIS LICENSE HAS BEEN PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
The "No Attribution" or "-0" license is a modification to the usual MIT license that also removes the requirement for attribution. It is roughly the same as an MIT license consisting of a sandwich of (paragraph, line, paragraph), but it is missing the middle line of the 'sandwich'.
The license may also be useful for code that is intended for developers to use as reference, teaching samples, examples, or base templates that other developers may modify for their own other purposes.
In many of these cases, the initial developer may not want to impose even the cost of attribution, or the use cases may not be conducive to attribution. While wanting the benefits of MIT-N Style terms.
The CC0 and various "do what you want" licenses and various public domain dedications may be less attractive to the initial developer for various reasons (i.e., a bare license is preferable to other license domains) The MIT license with all the attribution requirement language removed also addresses this need. In the same way that ISC Licenses (+Rights afforded after the Berne Convention) could, if similarly modified.
While researching prior to publishing this repo, an alternative option was discovered https://romanrm.net/mit-zero, which is an independent formulation and publication of a similar idea.
(the License Agreement File work itself shall eventually be available under any & every possible combination for dual/multi-license options including but not restricted to fallback terms of the WTFPL, Unlicense, MIT-0, and CC0.)