So far I've also emailed the FSF ([email protected]) and am currently awaiting a response.

My understanding (which may be incorrect) is that the FSF actively defends copyright on GNU projects. They do not defend other projects, but they will consult with attorneys on matters of the licenses themselves.

Nevertheless, I (and I'm sure many others here on HN) would enjoy seeing the response from the FSF.

Praat includes code from the GNU Scientific Library (GSL)

Maybe the Software Freedom Conservancy would be more suitable?

https://sfconservancy.org/

I think libgcrypt is a GNU project.

This honestly is a really good reason for (A)GPL projects to use at least one GNU (A)GPL licensed dependency.

If someone does violate the license on your code, they are also transitively doing it to a bigger, angrier fish as well.

>not simply roll over and give up their source code

Nothing requires them to give over the source code. They just have to stop distributing the software which is violating the license.

They've already distributed the software. They are required per the license to distribute the source code. They can remove the source code that requires them to do this, but existing copies of the software must are covered under the license agreements.

i.e. The cat is out of the bag.

They were also required by the license to follow the licence and yet here we are. They’re in violation of the license. They can be sued for damages.

That is not how it works. It was copyright infringement for them to distribute the binary without the source code. If they are made aware of this and they continue to distribute it then it becomes willful infringement each time they distribute it.

Even they you were to distribute the code after the fact that doesn't forgive the copyright infringement they did early. In the end releasing the code doesn't do anything for them other than give away their IP. The best option in this scenario for them is to stop distributing the binary to avoid willful infringement and then work to remove the GPL code from the project and then start distributing it again.

Do remember that the GPL is not a EULA. It only applies when you make copies of the code.

Also random people can't sue over this infringement. Only the copyright owner of the code can do so.

> If they are made aware of this and they continue to distribute it then it becomes willful infringement each time they distribute it.

They have been made aware via email, and they continue to distribute it via the download link. The is no need to couch this as a hypothetical scenario.

I was talking about in general. Yes, in this case they are choosing to take on legal risk. This is typically fine because almost no one ever sues over free software.

This is not "fine" even if no one ever sued over Free Software.

There are different version of "fine" here :)

Morally, it's definitely NOT fine.

It will probably have no significant bad effect on their business, iow, it is fine from a business perspective.

It's unfortunate, but likely true.

I could be wrong, but I think you misunderstand how the GPL works. The GPL doesn't require distribution of the source code along with the binaries. Most organizations do that because it's easier than the other option, which involves providing the source code to users of the software on request.

So they aren't actually infringing the copyright unless they not only don't provide the source publicly, but also don't provide it on request for at least three years.

I was making a simplification. The license requires you to either distribute the source or distribute an offer on how someone can acquire the code.

   b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years

It also would require the written notice which they didn't do.

> existing copies of the software must are covered under the license agreements.

While this is true, it should be noted that we can't know which license will be applied at this point.

Remember that (L)GPL forces you to release your source code under some specific circumstances, and the implied condition here is that you have accepted the license in the first place. If you didn't ever agree to that license, you are clearly violating GPL but otherwise any other restriction of GPL doesn't immediately apply to you; it will have to be resolved in the court. And it is entirely possible that you and original software author(s) can reach an entirely different agreement that doesn't involve GPL at all. So as a user, you can't technically request for source codes right now. (Of course, it still is a not-too-bad strategy for users as original software authors can always demand GPL.)

Does usage constitute agreement?