From 4a13d61e25817f5d7211cfb0fabc53955306aff0 Mon Sep 17 00:00:00 2001 From: J Date: Wed, 2 Oct 2024 02:25:33 -0400 Subject: [PATCH] docs: indicate the license options (MIT, Apache 2.0, or Unlicense) of the project --- README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.md b/README.md index 3f478dc..9c797f5 100644 --- a/README.md +++ b/README.md @@ -29,3 +29,12 @@ To be more specific about what a breaking change _could_ entail: - changing the expected result of an existing integration test (not sure if unit tests would count) All the crates in this project have a [minimum supported Rust version (MSRV)](https://rust-lang.github.io/rfcs/2495-min-rust-version.html) of 1.76, the release succeeding [the one that stabilized `async fn` in traits](https://blog.rust-lang.org/2023/12/28/Rust-1.75.0.html) (which the `core` crate of this project is expected to make use of). I [intend to test this in CI (GitHub Actions) in the future](https://github.com/babichjacob/ac-qu-ai-nt/issues/5) to identify if it ever gets raised by changes but I have not set this up yet. Raising the MSRV will be considered a breaking change --- my justification is that it [seems more appropriate for an application like this](https://github.com/matklad/once_cell/issues/201#issuecomment-1257213601). This may be reconsidered if [Cargo's MSRV-aware resolver](https://rust-lang.github.io/rfcs/3537-msrv-resolver.html) is stabilized. + +## License + +All contents of this repository are licensed under either the +* [MIT license](LICENSE-MIT), or +* [Apache 2.0 license](LICENSE-APACHE), or +* [Unlicense](LICENSE-UNLICENSE) + +at your option.