This is a convertible software license that lets anyone run the code, and converts to the full MIT License under a sponsorship model.
Copyright 2019 Avaer Kazmer
Permission is hereby granted to run and distribute verbatim copies of this software for any purpose.
The copyright holder additionally grants an MIT License to this software to sponsors per terms at https://github.com/sponsors/modulesio
The full text of the MIT License can be found at https://github.com/exokitxr/ismit/blob/master/MIT-LICENSE.txt
THE SOFTWARE IS 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 most common structure in open source software is a lone developer working a volunteer side job out of passion for the cause.
The majority of users, especially companies, copy-paste open source code under a permissive license and occasionally request bugfixes and features from the developer. Larger open source projects are funded by companies, but the dynamic remains -- a couple of developers justifying open source to their employer.
This works until the developer burns out or needs to attend to their "real job" instead, at which point users feel abandoned, and the developer is held irresponsible.
This license breaks the cycle by aligning developer and user incentives. Everyone gets the liberty they expect from their software. Where this liberty burdens the maintainer with responsibility -- code changes -- that responsibility is shared in the form of a sponsorship.
If it doesn't work out, no problem! Sponsors keep the permissive license for their copy of the code -- including the right to fork and re-release the software.
In the meantime, the developer has a reason to maintain the software users want. Companies have a line item to expense for the software they use.
Yes, for any purpose, as long as you don't change it. To change it, you need the MIT License.
It probably doesn't. Most use cases just import and run the code somewhere; the license explicitly allows that.
If you are a company looking to reshape the code into your product, you might want to sponsor a permissive MIT License.
Yes, keeping in mind the rest of the terms.
Yes.
Yes, as long as you don't change it. To change it, you need the MIT License.
Yes, without changes. If you are making changes, you need the MIT License.
Yes, if that version of the code came with this license.
No, that would be deriving a modified version. The MIT License allows this, of course.
Yes, the text is literally the MIT License.
Yes -- the MIT License says you can!
Yes, but the MIT License applies to the version of the code you got while you were a sponsor only.
Nothing, you get to keep any license you have. You might be less inclined to sponsor the software in that case.