3 ms·
Thanks for the link; sadly none of the links to the repo can be viewed to see what exactly occurred. To those downvoting, curious why? Many of the links are n
by amszmidt 9mo ago
Thanks for the link; sadly none of the links to the repo can be viewed to see what exactly occurred.
To those downvoting, curious why? Many of the links are not viewable, since GitHub hides them, so any discussion becomes quite tricky.
- kstrauser 9mo agoI didn't downvote. I suspect people did because it sounded like you were defending ILoveRockchip's actions, based on either 1) not understanding what they did, and/or 2) not having access to the facts. People get snippy about abusing Free Software.
- progval 9mo agoYou can find an archive of the links' targets at https://archive.softwareheritage.org/swh:1:dir:5861f191873366a1a6b18bdeacee9a55d2d8cb49;origin=https://github.com/rockchip-linux/mpp;visit=swh:1:snp:65c3ea2995fea50c556ae4fc2305e6b2bad6e4a3;anchor=swh:1:rev:437bfbeb9567cca9cd9080e3f6954aa9d6a94f18;path=/mpp/codec/dec/ https://archive.softwareheritage.org/swh:1:dir:5861f19187336...
- justinclift 9mo agoInterestingly, the repo has a LICENSES folder that contains the text of the licenses used in the repo: https://archive.softwareheritage.org/browse/directory/ed4b20403539eaf089df673d36013b4ecabceecb/?origin_url=https://github.com/rockchip-linux/mpp&path=LICENSES&revision=437bfbeb9567cca9cd9080e3f6954aa9d6a94f18&snapshot=65c3ea2995fea50c556ae4fc2305e6b2bad6e4a3 https://archive.softwareheritage.org/browse/directory/ed4b20... And yep, they only included the most openly permissive ones there (APL2 and MIT), completely skipping everything else. Ugh.
- nottorp 9mo agoMaybe because if the ffmpeg people say they have a reason and they've waited 1 year and a half for compliance, we trust them more than whoever relicensed their code without permission.