(Replying to PARENT post)
The security angle is because fixing a vulnerability is a fairly compelling reason why someone might want to update the software in a device they've purchased. Vulnerabilities found in Linux and other GPL'd software often get fixed fairly quickly, but random Linux-based IoT devices and whatnot often ship with ancient versions of GPL'd software and never see any security fixes. ("The S in IoT stands for security.") If the vendor complies with the GPL, then end-users can patch it themselves. But, many vendors don't, hence the need for the new mailing list.
(Replying to PARENT post)
If it had been a sentence from the article itself, we might have kept it, because "Prioritizing software right to repair: engaging corporate response teams" doesn't say much. But I couldn't find that language in the article, and it seems you couldn't either, so it's probably best to stick to the rule in this case and revert it.
(Replying to PARENT post)
(Replying to PARENT post)
> We recently launched Use The Source (alluded to above), which helps device owners and companies see whether source code candidates (the most important part of copyleft compliance) are giving users their software right to repair, i.e. whether they comply with the copyleft licenses they use.
(Replying to PARENT post)