this post was submitted on 27 Dec 2025
136 points (98.6% liked)

Technology

78002 readers
2849 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
L4s@hackingne.ws
136
GitHub Takes Down Rockchip MPP Repository After FFmpeg Copyright Claim (linuxiac.com)
submitted 1 day ago by throws_lemy@lemmy.nz to c/technology@lemmy.world
13 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] Scafir@discuss.tchncs.de 4 points 3 hours ago

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:

  1. 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
  2. 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)