unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: <tomas@tuxteam.de>
Cc: emacs-devel@gnu.org
Subject: Re: Gathering data on user preferences
Date: Wed, 08 Sep 2021 07:52:20 +0000	[thread overview]
Message-ID: <874kavh5cb.fsf@posteo.net> (raw)
In-Reply-To: <20210907064208.GB4097@tuxteam.de> (tomas@tuxteam.de's message of "Tue, 7 Sep 2021 08:42:08 +0200")

<tomas@tuxteam.de> writes:

> 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".

[...]

> 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?).

At this point, couldn't the information attached to bug reports be
used. I remember someone making the suggestion in last years
discussion. The advantage is that there is already a lot of data
available right now, and that this data contains the evolution of trends
over a number of years.

I might also imagine that if people knew bug reports contribute to a
better representation of the entire user-base.

-- 
	Philip Kaludercic



  parent reply	other threads:[~2021-09-08  7:52 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
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 [this message]
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=874kavh5cb.fsf@posteo.net \
    --to=philipk@posteo.net \
    --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).