<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I’m OK with changing the license, otherwise qemu can’t make use of the rust-vmm components.<br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">2022年7月5日 下午9:37，Andreea Florescu <<a href="mailto:andreea.florescu15@gmail.com" class="">andreea.florescu15@gmail.com</a>> 写道：</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">Gerry, Rob, Sebastien, what do you think about this?</div><div class="">I would like to go ahead with the license change to Apache 2.0 OR BSD-3-Clause and it would be great to also get an ACK from you.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Andreea<br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 30, 2022 at 10:01 AM Andreea Florescu <<a href="mailto:andreea.florescu15@gmail.com" class="">andreea.florescu15@gmail.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr" class=""><div class="">I just wanted to clarify something as well, I do not feel strongly about changing the license to BSD-3-Clause, we can also use Apache 2.0 OR BSD-3-Clause if that makes sense. My interest is to fix the problem initially reported which significantly limits the usefulness of this project as it cannot be used by projects like QEMU.<br class=""></div><div class="">As most contributions are coming from Google (indirectly), Amazon, Intel and Alibaba, it would be really helpful to also get input on updating the license from the folks that are contributing from the respective companies. From the Amazon side of things, we discussed this internally and we're onboard with the change.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Andreea<br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 23, 2022 at 1:48 AM Jeremy Stanley <<a href="mailto:fungi@yuggoth.org" target="_blank" class="">fungi@yuggoth.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2022-06-22 17:30:37 +0100 (+0100), Alberto Faria wrote:<br class="">
[...]<br class="">
> I may be misunderstanding this, but it sounds like you're assuming<br class="">
> that Apache-2.0 is a superset of BSD-3-clause in terms of user<br class="">
> obligations. I have no idea if this is actually the case or not, but<br class="">
> if it is, then "Apache-2.0 OR BSD-3-clause" == "BSD-3-clause", which<br class="">
> in a sense contradicts the wide use of the former in Rust crates.<br class="">
[...]<br class="">
<br class="">
I'm not a lawyer, but my long-time understanding has been that when<br class="">
you distribute software under "license x or license y" that allows<br class="">
people who are receiving and possibly redistributing and deriving<br class="">
that software to do so based on their choice of either license.<br class="">
Blanket statements like this are rarely helpful however when the<br class="">
software consists of parts under different licenses, such as<br class="">
shipping some files under BSD-3-clause and other files under<br class="">
Apache-2.0 as part of the same project. Under those circumstances,<br class="">
the sum total of the software is effectively held to the union of<br class="">
the requirements for both licenses, but for permissive-style<br class="">
licenses like these it's also not expected that the licenses of some<br class="">
files impact the licenses of the other files, so long as the chosen<br class="">
licenses have compatible terms (permissive-style licenses do not<br class="">
require you to distribute derivative works under the same terms).<br class="">
<br class="">
The situation changes dramatically when copyleft-style licenses are<br class="">
involved, since they often (as is the case with GPL for example)<br class="">
convey transitive requirements which forbid additional licensing<br class="">
requirements on the complete work and require redistribution under<br class="">
the same license instead.<br class="">
<br class="">
As for whether Apache-2.0 is a superset of BSD-3-clause, that's<br class="">
implied by its ancestry, since the original Apache license was<br class="">
effectively a direct copy of BSD-4-clause, and then for Apache-1.1<br class="">
the authors dropped the advertising clause that Berkeley had also<br class="">
dropped, making it then equivalent to BSD-3-clause. Apache-2.0 is a<br class="">
superset of the requirements of Apache-1.1 (and so BSD-3-clause) as<br class="">
it merely adds a grant of patent license to the original terms.<br class="">
-- <br class="">
Jeremy Stanley<br class="">
_______________________________________________<br class="">
Rust-vmm mailing list<br class="">
<a href="mailto:Rust-vmm@lists.opendev.org" target="_blank" class="">Rust-vmm@lists.opendev.org</a><br class="">
<a href="http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm" rel="noreferrer" target="_blank" class="">http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm</a><br class="">
</blockquote></div>
</blockquote></div>
</div></blockquote></div><br class=""></div></body></html>