License?
Hi there, thanks so much for these weights! I've got it running smoothly now. I'm just curious--what license is this released under? The only one I could find linked from the many sources would be the AGPL-3.0 license on the original Mika-7b model. Just wanted to clarify. Thanks!
I just keep the same Licence as the full weights from the Merge:
https://huggingface.co/Nitral-AI/Mika-Longtext-7b
Which is None, haha. Removed: Other
Let me know if that would be an issue.
Hmm...it looks like the original models are licensed differently:
- https://huggingface.co/Epiculous/Fett-uccine-7B uses AGPL3
- https://huggingface.co/mistralai/Mistral-7B-v0.1 uses Apache 2.0
According to a completely different LLM that I asked this question to:
Apache License 2.0 and AGPLv3 Key Differences
Apache 2.0 is a permissive license that allows for nearly unrestricted freedom to use, modify, and distribute the licensed work. It has requirements for copyright notice, license notice, and a change notice if changes were made, but it doesn't require that derivative works or modifications be open-sourced under the same license.
AGPLv3 is a strong copyleft license similar to the GNU General Public License (GPL), but with an additional term that requires you to make the source code available for modified versions that are used over a network. AGPLv3 is designed to ensure that all derivatives of the code, or any code that links to it, remain open source under the AGPLv3.
Compatibility
The Apache 2.0 license is generally considered to be compatible with the GPL version 3 (GPLv3), which means Apache 2.0 licensed code can be included in GPLv3 projects. However, the reverse is not allowed because the Apache license has some requirements that are not compatible with GPLv2. Since AGPLv3 is an extension of GPLv3, it inherits its compatibility with Apache 2.0 in a one-way direction.
You can include Apache 2.0 licensed code in an AGPLv3 project, but the combined work would effectively need to be licensed under AGPLv3 to comply with the AGPLv3's requirements on network use. This means that while you can merge Apache 2.0 code into an AGPLv3 project, you cannot take AGPLv3 licensed code and relicense it under Apache 2.0.
Practical Implications
If you plan to merge an Apache 2.0 licensed library with an AGPLv3 licensed library, the resulting project must comply with the terms of the AGPLv3, given its stricter requirements. This is crucial for ensuring that your use of the libraries respects the legal requirements and intent behind the open source licenses.
Recommendations
Review the Licenses: Read both licenses in full to understand their requirements, focusing on sections related to redistribution, making derivative works, and copyright notices.
Consult with Legal: If there's any doubt or if the project is of significant scale, complexity, or importance, consulting with legal counsel or an expert in open source licensing is advisable.
Consider Community Practices: Look at how similar projects may have handled the merging of libraries under these licenses, as there may be established practices or consensus in the open source community.
In summary, while merging Apache 2.0 and AGPLv3 licensed code is technically possible, the combined project would need to be distributed under the terms of the AGPLv3. Always ensure you understand the legal implications and comply with the license terms.
So probably would best/easiest be under the AGPL3 license, by my understanding.
I'll follow the same license as the original model weights -- https://huggingface.co/Nitral-AI/Mika-Longtext-7b -- so Ideally inform the Author to update theirs and I'll match it on the respective quants right away.
I'm not the merge author. :')