But the fact that the FSF hasn't in fact litigated isn't by itself a reason that preserving the clear ability to litigate isn't useful. We don't know how many cases an infringer was made more likely to come into compliance by the fact that work had clear ownership, particularly because the FSF has avoided litigation when they had other avenues open.
It is easier if they own all the code, but it isn't required.
It's not that simple. For joint works any single author can grant rights to the entire work. Do you know what the caselaw is regarding joint works as applied to typical FOSS projects? I don't. But I suspect it's less than crystal clear (see, e.g., https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2999185) and therefore creates significant risk when attempting enforcement. Litigation is costly, and a wrinkle like this could potentially be exploited by an infringer to drag out an enforcement case for many years.
That doesn't sound right - why would anyone ever contribute to a joint work if the other author can sell it to a publisher on their own? Wouldn't they then just take all the royalties and leave you with nothing?
2) A joint author still must share profits. See previous link and also https://repository.law.umich.edu/cgi/viewcontent.cgi?article... (But can a joint author claim waste--loss of commercial profit--if another licenses as FOSS?)
3) Joint authors in the business of commercializing their works (as opposed to accidental joint authors) would usually have a contract between themselves controlling licensing.
4) If it doesn't sound right, that's exactly my point. Copyright law is more complex than discussed on internet forums. Just because something doesn't make sense to a non-practitioner doesn't mean it's completely senseless to a practitioner. Corporate lawyers are often much more risk averse than law professors counseling FOSS advocacy organizations. But as mentioned by the previous SSRN paper I linked[1], joint authorship is typically considered to be detrimental and even fatal to the objectives of many FOSS licenses, which usually assume a model of distinct, serial contributions creating derivative (not joint) works.
[1] Chestek, Pamela S, A Theory of Joint Authorship for Free and Open Source Software Projects (July 2, 2017). Available at SSRN: https://ssrn.com/abstract=2999185 or http://dx.doi.org/10.2139/ssrn.2999185
To be clear, I'm not trying to say that all or even any FOSS works are or should be considered joint works. Just that the possibility could be a concern for lawyers contemplating enforcement. Certainly in other areas where you often see informal cooperation in the creation of collaborative works, such as in music, the issue absolutely does come back to bite people.
I mean, it's true that you could still win a case having to win those arguments, but it's harder.
Defense in depth isn't just a computer security technique. Any lawyer will tell you that the easiest argument to win is one that can't be brought in the first place.
IANAL but I don't think it works that way. They could pay up $X for damages and even get their license revoked. They still don't buy a license to perpetually violate the GPL.
There isn't much case law here. It will probably end up in appeals for years. In the end it doesn't really benefit anyone to take their chances in court.
You basically say that the court can order the copyright holders to offer an exclusive proprietary license to the violators for a "reasonable" price.
Isn't there any case law for license violations in general? For the purpose of this discussion this is just yet an other license violation, not necessarily tied to the GPL.
Also statutory damages for willful infringement are very high As much as 150k per work which again still doesn't grant you a license.
Also, what if a company decides to ignore the GPL and pay up? The courts and law understand monetary damages. The FSF runs the risk of the judge deciding that the code is already out there, and the value the code is $X: therefore the infringer should reasonably buy a license for $X and doesn't have to give source code back. This would violate the spirit of the GPL, but would fit the letter of the law.