3 ms·
This describes, as far as I can tell, the de facto enforcement practices of ONE GPL copyright holder. I don't see where it places any binding limits on even the
by microtherion 8y ago
This describes, as far as I can tell, the de facto enforcement practices of ONE GPL copyright holder. I don't see where it places any binding limits on even the enforcement the SFLC would take, and of course it has no power to enforce any limits whatsoever on other GPL copyright holders.
In the particular case of Kernel development, contributors are NOT required to assign their copyrights to any shared institution, are perfectly within their rights to take any enforcement action against violators that they wish, and sometimes do exercise that right: https://www.zdnet.com/article/linux-beats-internal-legal-threat/ https://www.zdnet.com/article/linux-beats-internal-legal-thr...
- letstrynvm 8y agoBit sad you have no idea what you're talking about https://www.kernel.org/doc/html/v4.17/process/kernel-enforcement-statement.html https://www.kernel.org/doc/html/v4.17/process/kernel-enforce... ... but keep digging anyway.
- dang 8y agoPersonal swipes will get you banned here, regardless of how wrong or ignorant another commenter is (or seems). If you'd please review https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html and follow the rules when posting to HN, we'd appreciate it.