There are a few ideas of how trouble could arise off the top of my head. None 
of this is going to be nearly as exhaustive as an expert legal opinion could be.

You only need to look at the YouTube musician debacle for an example.

Musicians on YouTube are completely unprotected and so people upload their 
music, then someone else copyrights it, and then claims the copyright.

Shaky ownership of copyright of included code could easily result in a weak 
position when such challenges arise for GHC in the future.

The tech industry has a history of companies making their whole existence out 
of suing thousands, hundreds of thousands of companies and people. "Piracy 
lawsuit" companies. Patent trolls. DMCA trolls. Etc. It is easy to imagine that 
in the future, a company could arise that:

1. Has identified that (some/every) AI training corpus included their 
copyrighted work
2. Deems any work generated by that AI to be derivative of their copyright
3. Harvests git repositories for people's emails from commits authored by John 
Doe "and claude"
4. Sends out one million fine / settlement demands

Let's say they estimate the Haskell industry, which includes banks, high 
frequency traders, insurers, crypto, and other juicy steaks, to be worth $100M 
to them and that's their demand. What do we do then? Nothing, we're just in a 
deep hole, because Laurent de Cotret decided "this isn't Haskell-specific".

You asked for an example. Here is one. I want to specifically preclude a 
conversation resulting from this that goes like:

1. "OK, I see your problem"
2. "But, aha! <some objection>"
3. "Therefore, there is no problem"
4. "So, we don't need experts looking into this."

I will not be going down this road. Even if my simple example above which I 
came up with in 15 seconds of thinking is provably never going to happen, there 
can be other scenarios. This is just one thing to illustrate how things could 
go, but again, it's up to the experts to tell us what problems could *actually* 
arise.
_______________________________________________
ghc-devs mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to