unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: tomas@tuxteam.de
Cc: emacs-devel@gnu.org
Subject: Re: Gathering data on user preferences
Date: Tue, 07 Sep 2021 17:54:09 +1000	[thread overview]
Message-ID: <87czpklsng.fsf@gmail.com> (raw)
In-Reply-To: <20210907064208.GB4097@tuxteam.de>


<tomas@tuxteam.de> writes:

> [[PGP Signed Part:Undecided]]
> On Tue, Sep 07, 2021 at 01:22:46PM +1000, Tim Cross wrote:
>> 
>> Recent threads on proposed changes to default settings, provision of
>> configuration profiles, surveying Emacs users etc make me wonder if we
>> could use ELPA more effectively to gather valuable data on settings of
>> interest.
>> 
>> My thinking is that we could create an ELPA package [...]
>>                            [...] for users to submit details about
>> their current settings which could be used to help inform decisions
>> regarding default settings.
>
> Basically a good idea. There's well-established precedent with
> Debian's popcon [1]. At install you are asked whether you want
> to take part in it, the default being "no". So it is active
> "opt in".
>
> The original idea was to have some basis for deciding which packages
> go into the first CD (remember those?).
>
> Some preliminary work has to be done by Someone [TM]. For example,
> you wouldn't like your IMAP account credentials published in some
> statistics :-)
>
> I.e. some categorising of variables into publishable and private
> (perhaps with more than just two levels? Decisions, decisions)
> seems in order (reminds one of that "safe variable" thing, doesn't
> it?).
>
> So I think some discussion and some design work are needed; but it
> seems a good idea. And popcon (impressively) shows that it actually
> /can/ work.
>

I was thinking of only getting data on 'non-sensitive' variables and
only aggregate data would be available (i.e. make sure it is not
possible to say person x submitted values a, b and c). It could possibly
even be setup as a very simple web service which just accepts a JSON
object in the body of a POST request. That would avoid anyone having to
provide an email address. The possible downside is that this would be
open to 'gaming' the system, but I'm not sure we need to worry about
that too much - there is little reward in doing so.

The system would definitely be 'opt in' and the user would be shown
exactly what is going to be sent (and provided with the ability to
remove anything they are not comfortable with). 



  reply	other threads:[~2021-09-07  7:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07  3:22 Gathering data on user preferences Tim Cross
2021-09-07  4:25 ` Howard Melman
2021-09-07  6:28   ` Eli Zaretskii
2021-09-07 13:22     ` Howard Melman
2021-09-08 13:37       ` Philip Kaludercic
2021-09-07  6:42 ` tomas
2021-09-07  7:54   ` Tim Cross [this message]
2021-09-07  8:11     ` tomas
2021-09-07  9:09       ` Tim Cross
2021-09-07 12:32         ` Arthur Miller
2021-09-07 13:48           ` Tim Cross
2021-09-07 14:52             ` Arthur Miller
2021-09-07 16:53               ` Tim Cross
2021-09-07 18:46                 ` Arthur Miller
2021-09-07 23:14                   ` Tim Cross
2021-09-08  7:52   ` Philip Kaludercic
2021-09-08  8:14     ` Tim Cross
2021-09-08 10:41       ` Daniel Fleischer
2021-09-08 13:02         ` Tim Cross
2021-09-08 12:52       ` Philip Kaludercic
2021-09-08 13:00         ` Tim Cross

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: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87czpklsng.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=tomas@tuxteam.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://git.savannah.gnu.org/cgit/emacs.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).