diff options
author | Kristóf Marussy <kristof@marussy.com> | 2023-08-24 00:44:03 +0200 |
---|---|---|
committer | Kristóf Marussy <kristof@marussy.com> | 2023-08-24 01:17:45 +0200 |
commit | 4114bea88de7e4d8ce5fb93d1f322d2c75835c2f (patch) | |
tree | 996a861046dfb7d007767b4d7aa4ae01ce108d12 /subprojects/language-semantics/src/main/java/tools | |
parent | refactor(web): clean up graphviz visualization (diff) | |
download | refinery-4114bea88de7e4d8ce5fb93d1f322d2c75835c2f.tar.gz refinery-4114bea88de7e4d8ce5fb93d1f322d2c75835c2f.tar.zst refinery-4114bea88de7e4d8ce5fb93d1f322d2c75835c2f.zip |
chore: clarify permissing licensing
For permissive licenses like MIT and BSD, OR EPL doesn't make sense, because the
copyright original permission notice must be retained at all times.
For code simply copied with minimal modifications that are unrelated to
Refinery, we can just use the plain MIT license or BSD-3-clause license.
For code with complex modifications related to Refinery, we can instead use the
MIT AND EPL-2.0 SPDX expression, which forces downstream users to retain the
original MIT notices as required by the MIT license, but also extends Refinery's
copyleft to our modifications.
Diffstat (limited to 'subprojects/language-semantics/src/main/java/tools')
0 files changed, 0 insertions, 0 deletions