Paul Wise writes:
>> Should I ask on debian-devel?
>
> Seems reasonable.
I did that here:
https://lists.debian.org/debian-devel/2016/11/msg00252.html
--
Brian May
Hi List,
On Mon, Nov 07, 2016 at 04:32:46PM +0100, W. Martin Borgert wrote:
> If Django implements usage analytics, I would strongly suggest to make it
> "opt-in" in Debian, just as popcon, not "opt-out".
FWIW as a long-time Debian user and supporter, I expect every piece of
software I install *n
Quoting Barry Warsaw :
I'd love to know if there's a Debian-wide policy on such things. E.g. if
"opt-out with informed user consent" was an official policy that we could
clearly point to and reference, it would greatly help provide
guidance to both
Debian maintainers and upstreams.
In the i
On Nov 07, 2016, at 01:21 PM, Brian May wrote:
>Should I ask on debian-devel?
I think you should, and I'll be very interested in that discussion.
Several packages in our team already apply deltas to upstream to disable
certain amounts of information gathering and reporting. The most common
exa
On Mon, Nov 7, 2016 at 12:06 PM, Paul Wise wrote:
> Making it opt-in with *informed* user consent.
Thinking on it more, due to the whole click-through culture on the
modern web, I'm not sure that informed user consent is quite enough.
Some discussion of that phenomenon in the latest FaiF episode:
On Mon, Nov 7, 2016 at 10:21 AM, Brian May wrote:
> I think upstream Django have requested our feedback on this pull request:
>
> https://github.com/django/deps/pull/31
I would suggest a few things:
Making it opt-in with *informed* user consent.
Use a Django-hosted piwik/etc service instead of
6 matches
Mail list logo
