-
Notifications
You must be signed in to change notification settings - Fork 172
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
LGPL license violation reported by upstream FFmpeg #530
Comments
I should note, if the project contributors are aware of any other misuse of licensed open source code, it's best to include removing or fixing those areas too. Chances are this isn't the only example, if that were the case. |
From a brief look, I see a large number of clear violations. At least
are clearly derived from libavcodec source code, as is obvious from the same code structure and naming, identical comments in the code, and sometimes even references to av_* functions and libavcodec. |
This violation was caused by the developer's insufficient understanding of the compatibility between licenses. They apologized deeply and said they would fix it as soon as possible and strengthen their learning about open source licenses. They also thank the open source community for pointing these out and welcome any suggestions and guidance. https://twitter.com/HermanChen1982/status/1761231278962364815 commented by @HermanChen at Rockchip |
So new release, still no change, or the changes pushed not counted as release:) |
Where’s the new release? IMHO they use tag as public release. |
Yeah there was bunch of new commits in the repo i thought it was a realease, seems not. Still im oss policing around :) |
So far we are fixing rk3576 issues. Quit a busy time. |
so still not doing anything about it? |
Please fix this license violation as soon as possible (it should be top priority, above any other issues you have), otherwise we will have to issue a takedown request to github. |
Thank you for your kind reminder, we are working on it |
The hevc, vp9 and av1 code will be fixed. |
@ramiropolla FWIW they've had over 5 months to CTRL+H the misleading licenses. I find it...interesting how people still bother to do free work for this kind of hardware (after so so many years) when this is all they get in return. |
@HermanChen any update? |
Upstream FFmpeg on Twitter reported an LGPL license violation in MPP's code. If this was due to an oversight, it's best to correct it promptly to avoid further harming Rockchip's reputation in the open source community.
The text was updated successfully, but these errors were encountered: