c/technology · by throws_lemy@lemmy.nz · 231d

GitHub Takes Down Rockchip MPP Repository After FFmpeg Copyright Claim

https://linuxiac.com/github-takes-down-rockchip-mpp-repository-after-ffmpeg-copyright-claim/

164 points · 14 comments · view on lemmy.world

14 Comments

CaptainBasculin@lemmy.bascul.in · 69 pts · 231d (6 replies)

How do you even manage to break LGPL lmao all it asks for is attribution, which is like a few line changes on your LICENSE file.

otter@lemmy.ca · 101 pts · 231d (2 replies)

Relevant bit

The DMCA filing states that several files in the Rockchip MPP repository are derived from FFmpeg’s libavcodec sources. It lists AV1, H.265, and VP9 decoder files, and claims the copied code is clear because of matching structure, comments, and commented-out calls to FFmpeg functions with their original names.

Much of FFmpeg, including libavcodec, uses the GNU Lesser General Public License version 2.1. This license allows reuse, but only if certain rules are followed. These rules include keeping copyright notices, giving proper credit, and ensuring any shared code remains under an LGPL-compatible license.

The DMCA notice says Rockchip broke these rules by removing the original copyright and author details, claiming the copied code as their own, and sharing it under the Apache license, which does not meet LGPL requirements here.

avidamoeba@lemmy.ca · 16 pts · 230d (1 reply)

Sounds like something they should easily be able to comply with. If the relevant ticket in their internal issue tracker is given priority. 😅

michaelmrose@lemmy.world · 7 pts · 230d

Maybe. They cut and pasted the other guys stuff who knows what other stuff is there

Goodlucksil@lemmy.dbzer0.com · 24 pts · 231d

They're Chinese, they ain't bothering to read and change the License (especially if they don't have many english-speaking devs)

michaelmrose@lemmy.world · 8 pts · 230d

Cut and paste source code into your repo, which you can do, then offer the whole thing under apache which you cannot do.

markz@suppo.fi · 3 pts · 231d

I didn't look into how the code is used, but LGPL can still easily get an entire project.

punrca@piefed.world · 41 pts · 231d (2 replies)

Most people are unaware that even open source projects have licenses: Permissive license, Strong Copyleft, Weak Copyleft etc.

Some resources:

frongt@lemmy.zip · 18 pts · 231d (1 reply)

And all those licenses rely on copyright and IP law.

0x0@infosec.pub · 4 pts · 230d

And all those global faceless multicorps requiring you to agree to their 200 page eula rely on that foss licensed goodness, without ever contributing an iota back to the source.

zurohki@aussie.zone · 28 pts · 231d (1 reply)

I just wish each video decoder manufacturer didn't feel the need to create their own API that isn't supported by anything.

whaleross@lemmy.world · 7 pts · 230d

It feels counter productive when everyone relies on ffmpeg and there are no proprietary secrets left to protect. Just agree on an open standard that saves time and effort for all companies using it while getting tons of goodwill and positive cosmic vibes and maybe even revenue.

frongt@lemmy.zip · -14 pts · 231d (1 reply)

Does this accomplish anything? Was anyone actually relying on this? I'd say the company was just doing it just to publish it, but I've known developers who would certainly use the public repo as the primary copy.

Scafir@discuss.tchncs.de · 12 pts · 230d

I believe it does. Weakly reciprocal license like LGPL is not equivalent as a permissive license like Apache. I see two main things on the top of my head:

This ensure that no one can license wash ffmpg and e.g. use rockchip's repo to distribute their own private product based on ffmpeg without publishing their changes
It ensures proper attribution of the work, which can have an impact on the developer's careers and ffmpeg as a whole.

On top of this, it really should not be complicated to license this code properly (unless rockchip wants to allow point 1, which is illegal)