New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FIX ALREADY!! fix camellia-r-oss and release camellia-t-oss | 修复camellia-r-oss并发布camellia-t-oss!!! #8268
Comments
Please stop.Don't spam this repository with these meaningless issues. Xiaomi is definitely going to ignore more legitimate requests if you continue spamming. They're a big company and have no responsibility to open source any of their code. You have to acknowledge the fact that you're essentially asking a large corporation to publish trade secrets. Once again, please stop. Do not spam these repositories. This isn't even an "issue" in the first place. Write to Xiaomi directly, and again, do not spam. |
Please stop. |
Wow |
You do realize that the original Linux kernel source uses GPLv2 license meaning they have to release it either ways as they are violating the GPL by not providing compilable code or even functional code. FSF (Free Software Foundation) can take action against it as they do care about open source licenses. Also since Xiaomi released back then fully functional source for their devices, it doesn't really count as a "trade secret". |
This is an oversimplified and misinformative view on GPLv2's terms. The GPLv2 license has several loopholes which allow the proprietary redistribution of modified OSS source code. It is absolutely a trade secret. Leaking and reverse-engineering it without permission from the proprietor, is illegal. I highly doubt Xiaomi, a huge tech giant, would overlook this. Take note of Red Hat's closure of RHEL (and other products...) source code which contain source available forks and modifications to not just the Linux kernel, but other GPLv2 licensed projects. Don't like it? Don't use the software. |
No description provided.
The text was updated successfully, but these errors were encountered: