gt; business, but hard to do in an open source project unless you limit access
>> to the data to a few people. (Even if you ask users for permission to gather
>> data, I am quite sure, you still need a privacy policy.)
>>
>> Manuel
>>
>>
>>> From:
for permission to gather
> data, I am quite sure, you still need a privacy policy.)
>
> Manuel
>
>
>> From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of MarLinn
>> via ghc-devs
>> Sent: 09 December 2016 14:52
>> To: ghc-devs@haskell.org
>
to a few people. (Even if you ask users for permission to gather data,
I am quite sure, you still need a privacy policy.)
Manuel
> From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of MarLinn via
> ghc-devs
> Sent: 09 December 2016 14:52
> To: ghc-devs@haskell.or
On Fri, Dec 9, 2016 at 3:53 PM, Ben Gamari wrote:
> Simon Peyton Jones via ghc-devs writes:
>
> > Just to say:
> >
> >
> > · Telemetry is a good topic
> >
> > · It is clearly a delicate one as we’ve already seen from two widely
> > differing
Simon Peyton Jones via ghc-devs writes:
> Just to say:
>
>
> · Telemetry is a good topic
>
> · It is clearly a delicate one as we’ve already seen from two widely
> differing reactions. That’s why I have never seriously contemplated
> doing anything about it.
>
> · I’m love
many people are running each version of
their software.
Simon
From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of MarLinn via
ghc-devs
Sent: 09 December 2016 14:52
To: ghc-devs@haskell.org
Subject: Re: Telemetry (WAS: Attempt at a real world benchmark)
It could tell us which
It could tell us which language features are most used.
Language features are hard if they are not available in separate libs.
If in libs, then IIRC debian is packaging those in separate packages,
again you can use their package contest.
What in particular makes them hard? Sorry if this