> I have reached out (as I said I would) to the HF

Great stuff, very helpful. Thank you!

> our catalogue of questions

Maybe we could start building such a catalogue of questions.

> any competent lawyer specialised on IP rights should be able to either answer 
> our questions

Be very wary about this. In my experience it's easy for lawyers who appear 
competent - and even *are* competent - to absolutely bungle jobs. I think the 
main reason is people aren't good at estimating how competent a lawyer will be 
*in that particular situation*.

> or be able to refer to one that can.

Watch out for references too. Lawyers usually don't keep in touch with other 
lawyers at a professional level other than in adversarial situations. Any 
references are usually going to be based on friendship. The only time lawyers 
associate with other lawyers based on specialization and quality of work is 
when they become partners (or otherwise work in the same law company). In my 
experience lawyer references from other lawyers have a high chance of failure.

> risk assessment

agreed.

So now the question would be:

Why risk anything at all? Why risk decades of research and work by thousands of 
people? What are we winning that otherwise cannot be obtained at all?

I think this needs assessment of its own, and I think it's super important.

One common defense I've seen is "but then people will lie about their use of 
LLMs" - ok, and? If I'm a store clerk, and I'm given money, I'm not liable for 
where it came from, unless someone specifically tells me it came from a 
robbery. If people tell us they created things themselves, and they lied, then 
perhaps any copyright based quarrel would be possible to direct to that person 
(they lied and misled the project to accepting their derived, GPL-infected, 
stolen-IP code*) and deflect it off of GHC.

* I'm not saying all LLM code is like that, those are just some possible 
arguments.
_______________________________________________
ghc-devs mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to