I agree that we should maybe tone down a bit.

But I also feel the HF response was fairly disappointing:

- it says the topic is not Haskell specific, which is a bit
confusing... is gitlab infrastructure not Haskell specific either?
We're investing in all sorts of things that are not directly related to
the language, but to the ecosystem at large. Protecting our "assets"
legally is definitely one of them.
- it says "not good use of our resources", but didn't actually provide
insights as to why: e.g. is legal advice on that topic too expensive or
is it a waste of money? Why? I mean it may very well be, but we don't
have to get deep into crazy legal fees for a first consultation.
- it ends with a hint that there are actually relevant action points
(like... contacting the FSF), but then didn't seem to express any
interest in following up on those. I would have expected the HF to take
the lead here, because the success rate will be higher when it comes
from such a body. We have to advertise our interest in this issue and
not stand by passively.

Cheers,
Julian

On Fri, 2026-08-21 at 12:03 +0900, Moritz Angermann via ghc-devs wrote:
> > 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”.
> 
> Please don’t attack people.  As you can see from the emails you
> quoted yourself, Laurent merely relayed the message of the Haskell
> Foundation Board.  The decision was made by the board, not by Laurent
> alone; it shouldn’t be surprising that the boards chair is tasked
> with external communication.
> 
> _______________________________________________
> ghc-devs mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
_______________________________________________
ghc-devs mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to