From: Johannes Sixt <j6t@kdbg.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Thomas Braun" <thomas.braun@virtuell-zuhause.de>,
"Jeff King" <peff@peff.net>,
git@jeffhostetler.com, git@vger.kernel.org, gitster@pobox.com,
"Jeff Hostetler" <jeffhost@microsoft.com>
Subject: Re: [RFC PATCH v1] telemetry design overview (part 1)
Date: Sun, 10 Jun 2018 00:44:25 +0200 [thread overview]
Message-ID: <410f0fee-010c-c178-224c-e47ae0b0dda6@kdbg.org> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1806092241180.77@tvgsbejvaqbjf.bet>
Am 09.06.2018 um 22:43 schrieb Johannes Schindelin:
> On Sat, 9 Jun 2018, Johannes Sixt wrote:
>> When you want usage data, ask your users for feedback. Look over their
>> shoulders. But do not ask the software itself to gather usage data. It will be
>> abused.
>>
>> Do not offer open source software that has a "call-home" method built-in.
>>
>> If you want to peek into the workplaces of YOUR users, then monkey-patch
>> survaillance into YOUR version of Git. But please do not burden the rest of
>> us.
>
> We already offer hooks. You can do anything with those hooks. Even, if you
> do not pay close attention, to transfer all your bitcoin to a specific
> account.
>
> I agree with Peff: this is something you as a user need to be aware of,
> and need to make sure you configure your Git just like you want. As long
> as this is a purely opt-in feature, it is useful and helpful.
The problem with this feature is not so much that it enables someone to
do bad things, but that it is specifically targeted at recording *how
users use Git*.
> We do need it in-house, for the many thousands of Git users we try to
> support with a relatively small team of Git developers.
Then please build your private version and sell it to your thousands of
Git users. "in-house" == Microsoft? Small team of Git developers? So,
instead of shelling out the bucks for this extra burden, they put the
burden on the Community?
-- Hannes
next prev parent reply other threads:[~2018-06-09 22:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 14:53 [RFC PATCH v1] telemetry design overview (part 1) git
2018-06-07 14:53 ` [RFC PATCH v1] telemetry: design documenation git
2018-06-08 11:06 ` Ævar Arnfjörð Bjarmason
2018-06-07 21:10 ` [RFC PATCH v1] telemetry design overview (part 1) Johannes Sixt
2018-06-08 9:07 ` Jeff King
2018-06-08 16:00 ` Thomas Braun
2018-06-08 22:01 ` Johannes Sixt
2018-06-08 22:20 ` Ævar Arnfjörð Bjarmason
2018-06-09 5:03 ` Duy Nguyen
2018-06-09 6:31 ` Ævar Arnfjörð Bjarmason
2018-06-09 6:56 ` Jeff King
2018-06-09 20:05 ` Johannes Schindelin
2018-06-11 5:56 ` Jeff King
2018-06-09 7:31 ` Duy Nguyen
2018-06-09 6:51 ` Jeff King
2018-06-09 7:04 ` Johannes Sixt
2018-06-09 7:31 ` Jeff King
2018-06-12 16:04 ` Junio C Hamano
2018-06-09 6:56 ` Johannes Sixt
2018-06-09 20:43 ` Johannes Schindelin
2018-06-09 22:44 ` Johannes Sixt [this message]
2018-06-11 6:08 ` Jeff King
2018-06-10 0:00 ` brian m. carlson
2018-06-11 6:14 ` Jeff King
2018-06-11 8:30 ` Jeff King
2018-06-08 9:40 ` Ævar Arnfjörð Bjarmason
2018-06-08 15:46 ` Duy Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=410f0fee-010c-c178-224c-e47ae0b0dda6@kdbg.org \
--to=j6t@kdbg.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jeffhost@microsoft.com \
--cc=peff@peff.net \
--cc=thomas.braun@virtuell-zuhause.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).