chore: use AGPL-3.0-or-later spdx id in cargo.toml and readme
#42
Conversation
Signed-off-by: Rui Chen <[email protected]>
|
Hi @chenrui333 , I'm not opposed to this out of hand. Can you explain why this is necessary, or link to other information that explains why? Thank you! |
|
yeah, totally The patch just makes our licensing clearer by including an explicit AGPL-3.0-or-later identifier in both the Cargo.toml and the README. That way, anyone looking at the code or documentation knows exactly which license applies. It also helps ensure we stay consistent and compliant with how the project is distributed. |
|
Ok that makes sense. Is AGPL3.0 deprecated? My apologies, I have not kept up on any newer work with AGPL. |
yeah, pretty much from the license id perspective
|
👋 I feel like
AGPL-3.0-or-laterbetter suits the project thanAPGL-3.0-only, correct me if I am wrong. Thanks!closes #41
cc @ckampfe