doc(README): clarify license situation
Also, drop the top-level MIT license file. With this repository containing mostly Snix, it's confusing. Change-Id: I1215cf05f6f65b399ff7e8566d425b848fe9ccb0 Reviewed-on: https://cl.snix.dev/c/snix/+/30600 Autosubmit: Florian Klink <flokli@flokli.de> Reviewed-by: Vova Kryachko <v.kryachko@gmail.com> Tested-by: besadii
This commit is contained in:
parent
099f14194b
commit
afec95e269
2 changed files with 15 additions and 23 deletions
15
README.md
15
README.md
|
|
@ -7,3 +7,18 @@ of this repository.
|
|||
|
||||
It documents the status of this project, usage/development instructions, contact
|
||||
details and much more than what would fit in here. Seriously, check it out!
|
||||
|
||||
# License structure
|
||||
All Snix crates in this repository are licensed under GPL-3.0, with the
|
||||
exception of the protocol buffer definitions used for communication between
|
||||
services which are available under a more permissive license (MIT).
|
||||
|
||||
The idea behind this structure is that any direct usage of our code (e.g.
|
||||
linking to it, embedding the evaluator, etc.) will fall under the terms of
|
||||
the GPL3, but users are free to implement their own components speaking these
|
||||
protocols under the terms of the MIT license.
|
||||
|
||||
Other tooling in this repository might be licensed differently, and is usually
|
||||
described in the code itself, via some auxillary metadata (`Cargo.toml` etc), or
|
||||
a `LICENSE` file in the same or parent folder(s). If this is not the case,
|
||||
please open a bug!
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue