Open farshidtz opened 2 months ago
The MIT
license isn't a viral license like GPLv3
, GPLv3+
, or later versions. In fact, it's quite the opposite; MIT
is a permissive license, similar to Apache 2.0
and BSD
.
This means that: just because the libraries are licensed under MIT
doesn't mean that the application's code must be MIT
as well. We can choose to license the project under another permissive license if we wish. Our only obligation is to acknowledge that we're using libraries that are licensed under MIT
.
Our only obligation is to acknowledge that we're using libraries that are licensed under MIT.
That's exactly the problem. Every snap using the current Rust program needs to list MIT as one of its licenses, and provide the license text for it.
The project has no licensing. Ideally, this needs to be a loyalty free license to easily allow the use of the program in other snaps.
However, this isn't possible right now, given that the Rust code uses the following libraries: