[Rust-VMM] Licensing Issue in rust-vmm crates

Andreea Florescu andreea.florescu15 at gmail.com
Wed Jun 22 15:08:46 UTC 2022

[Resending this email from my personal email address as it seems like my
other email got into spam for most of you :(]

Hey folks,

afaria at redhat.com reported an issue [1] with the license of some of the
rust-vmm crates. In our first rust-vmm meetup we decided the license for
the crates to be BSD-3-Clause OR Apache 2.0 (as it's also specified in the
meeting notes available here [2]), but when we did the implementation of
the crate it looks like we wrote the license for some of the files and
crates as "Apache-2.0 AND BSD-3-Clause" instead. This license is
unfortunately incompatible with projects such QEMU, and makes the rust-vmm
crates impossible to use.

With this email I would like to get your agreement to update the license to
one that is compatible with QEMU and the other known customers of rust-vmm.
One thing that we need to discuss is what the license should be. As there
is code in vmm-sys-util coming directly from Crosvm I don't think a Apache
2.0 OR BSD-3-Clause license is appropriate because from my understanding
this would require the Crosvm code to be re-licensed as Apache 2.0 OR
BSD-3-Clause as well. I would like to propose to re-license it as
BSD-3-Clause as this is compatible with the licenses of all projects.

More details about the specific files where this is a problem are available
in the issue [1].


[1] https://github.com/rust-vmm/vmm-sys-util/issues/161
[2] http://lists.opendev.org/pipermail/rust-vmm/2019-May/000200.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20220622/729c20b2/attachment.htm>

More information about the Rust-vmm mailing list