Many open source licenses require some form of notice that you are using their code to be included in or included with the documentation of binaries you ship. I've used cargo-about to figure out what licenses we need to comply with in our own dependencies, and this PR represents draft work to get that reflected. Ideally we'd incorporate the cargo-about output to add something to the website, but I haven't done the work to sort that out myself yet.
Many open source licenses require some form of notice that you are using their code to be included in or included with the documentation of binaries you ship. I've used
cargo-about
to figure out what licenses we need to comply with in our own dependencies, and this PR represents draft work to get that reflected. Ideally we'd incorporate thecargo-about
output to add something to the website, but I haven't done the work to sort that out myself yet.