|
|
|
|
|
by onphonenow
1502 days ago
|
|
If you really want to pursue violations you COULD partner with SFC - the busybox developer did this. "As the ex-maintainer of busybox who STARTED those lawsuits in the first place and now HUGELY REGRETS ever having done so, I think I'm entitled to stop the lawsuits in whatever way I see fit. They never resulted in a single line of code added to the busybox repository. They HAVE resulted in more than one company exiting Linux development entirely and switching to non-Linux operating systems" - https://lwn.net/Articles/478361/ Here is the SFC's issue (came up when busybox replacements were discussed) "What can we do? The real problem here is that the SFC's reliance on Busybox means that they're only able to target infringers who use that Busybox code. No significant kernel copyright holders have so far offered to allow the SFC to enforce their copyrights, with the result that enforcement action will grind to a halt as vendors move over to this Busybox replacement." What's weird is despite NO significant copyright holder going along with SFC, they keep on marching forward as if they are backed by folks creating this code. |
|
This is why you don't want lawyers calling the shots. Lawyers are looking to get paid, they'd rather get a cash settlement than get the code. If the lawyers are working for you, the copyright holder, then you can choose how to handle the situation. But if you sign the code over to the lawyers, it will no longer be your call.