## 🚨 License Conflict

#7
by xixi126 - opened

Hi, I'd like to report a License Conflict in AtlaAI/Selene-1-Mini-Llama-3.1-8B. I noticed that this model appears to be fine-tuned from meta-llama/Llama-3.1-8B-Instruct, while being published under the Apache-2.0 license. Given the terms outlined in the LLaMA 3.1 Community License, especially regarding redistribution, attribution, and naming, this combination of licenses could potentially lead to legal or usage misunderstandings.

⚠️ Key violations of LLaMA 3.1 license terms:

Clause 1.b.i – Releasing derivative models must:
  • Include a copy of the original license  
  • Display “Built with Llama”  
  • Use “Llama” at the beginning of the model name  
  
Clause 1.b.iii – Must retain the following notice in the release:
   “Llama 3.1 is licensed under the Llama 3.1 Community License, Copyright © Meta Platforms, Inc. All Rights Reserved.”

🔹Suggestion:

1. It’s a good idea to explicitly include all key clauses of the LLaMA 3.1 Community License, such as:

  • A copy of the LLaMA 3.1 license in the repository or model card
  • A visible “Built with LLaMA” label on the model card, documentation, or UI
  • Using “LLaMA” at the beginning of the model name
  • Including the following notice in a “NOTICE” file or documentation:

    “Llama 3.1 is licensed under the Llama 3.1 Community License, Copyright © Meta Platforms, Inc. All Rights Reserved.”

  • A statement clarifying that use of the model must comply with Meta’s Acceptable Use Policy

2. Maybe we can just drop the Apache-2.0 tag and going with the LLaMA 3.1 Community License. This approach may help reduce potential confusion about redistribution rights and downstream usage conditions.

Thanks for your attention!

Sign up or log in to comment