License Compatibility

#1
by qiuqiu666 - opened

Hi , I’d like to report a potential license incompatibility in
grimjim/Llama-3-Luminurse-v0.2-OAS-8B-GGUF. I noticed that this quantized model was derived from grimjim/Llama-3-Luminurse-v0.2-OAS-8B ,
which is licensed under CC-BY-NC 4.0 — a non-commercial license.

Meanwhile, the downstream model is published under the LLaMA 3 Community License, which permits commercial use (within Meta’s framework) and is considerably more permissive.

⚠️ Key License Conflicts:

CC-BY-NC 4.0 (Upstream):
  • Prohibits all commercial use
  • Requires attribution
  • Must not be sublicensed under more permissive terms

LLaMA 3 Community License (Downstream):
  • Allows commercial use under certain conditions
  • Grants redistribution under the same license
  • Does not enforce upstream non-commercial use restrictions

Conflict:
→ CC-BY-NC-licensed content must **not** be reused in ways that enable commercial applications
→ LLaMA 3’s permissive redistribution and commercial clauses contradict the upstream NC restriction
→ Downstream users may mistakenly believe they have more freedom than the upstream license permits

🔹 Suggestions for Resolving

1. To align with CC-BY-NC 4.0 and LLaMA 3 license obligations:
  • Add a clear attribution in the model card specifying that this is derived from Llama-3-Luminurse-v0.2-OAS-8B under CC-BY-NC 4.0
  • Add a "NOTICE" or disclaimer noting that:
“This model includes material under CC-BY-NC 4.0 and is subject to non-commercial restrictions.”
  • Consider removing the LLaMA 3 license label, or replacing it with a dual-license notice stating that:
Commercial use of this model is not allowed due to upstream CC-BY-NC components
2. Alternatively, relicense the model under CC-BY-NC 4.0, to comply with the upstream’s most restrictive terms.

Let me know if I misunderstood anything — happy to help clarify further!

Thanks for your attention!

I'll change to CC-BY-NC 4.0 for now.

Clarified that restrictions of both licenses are inclusively in effect; if one forbids a use case, then it's forbidded. I do not believe it's possible to escape the original L3 license constraints.

Sign up or log in to comment