Re: [RFC PATCH v1] telemetry design overview (part 1)
- Date: Mon, 11 Jun 2018 04:30:58 -0400
- From: Jeff King <peff@xxxxxxxx>
- Subject: Re: [RFC PATCH v1] telemetry design overview (part 1)
On Mon, Jun 11, 2018 at 02:14:41AM -0400, Jeff King wrote:
> On Sun, Jun 10, 2018 at 12:00:57AM +0000, brian m. carlson wrote:
> > I also have to look at this issue from the interests of what is best for
> > the FLOSS community and for users as a whole. Adding in functionality
> > that sends off usage data from a command-line tool, especially one that
> > is as widely used as Git is, is not in the interests of users as a
> > whole, nor is it common practice in FLOSS tools.
> I'm not sure if this last statement is true. For instance, many tools
> have crash-reporting functionality, and some contain more advanced
> telemetry. E.g.:
> Personally I do not like this sort of data collection at all, and never
> enable it. And I would be highly suspicious of any FLOSS tool that
> shipped with it enabled by default. But it seems like at least some
> projects _do_ find it useful, and enough people enable it to make it
> worth carrying as a feature.
Re-reading what I wrote, I really want to emphasize something so that it
isn't missed. I think the important feature here is user consent, and
that seems to be the line that projects like Mozilla use (default to
off, and require explicit consent before sending anything off-host).
We don't have to use that line. I think "do not collect even locally" is
a reasonable line, because even collecting has performance and storage
management implications. And I don't think anybody is proposing to even
collect local telemetry without the user turning it on.
The line under discussion seems to be "implement code to collect
anything at all". That's a valid line, too, but IMHO it ends up blocking
useful features (and I think we already violate it with things like