unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Timothy <tec@tecosaur.net>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs Survey 2022 - design
Date: Sun, 02 Oct 2022 16:06:21 +0000	[thread overview]
Message-ID: <87edvq2osi.fsf@posteo.net> (raw)
In-Reply-To: <874jwma9cy.fsf@tecosaur.net> (Timothy's message of "Sun, 02 Oct 2022 16:30:48 +0800")

Timothy <tec@tecosaur.net> writes:

> Hi All,
>
> If any of you are wondering what happened to this, it has not been forgotten
> about! My very competitive todo list just pushed this on the backburner for a
> while.
>
> I’m returning to this now though, and hopefully will start testing the
> deployment and promoting the survey shortly (probably over the next few weeks).

First of all, I'd just like to thank you once more for taking it on
yourself to organise this!  I am looking forward to seeing the results!

> If anybody has last-minute “I really think you should change/add/remove this
> question” feedback, now would be the time to mention it. I think the current
> state of affairs is fairly decent though, and I don’t think it would be worth
> bikeshedding the questions 😛 — we can always refine/improve next year.
>
> The current set of questions:
> <https://github.com/tecosaur/emacs-survey/blob/master/config/survey.jl>

We have already been discussing this in private, but I'd like to re-post
it here for others to comment on:

    Timothy writes:

    > Philip Kaludercic writes:
    >
    >> I remember that “residence” was at least one more option that was
    >> discussed, and I still think that it is preferable to nationality.
    >
    > Why? It seems like a worse option to me.
    >
    >> doesn’t even have need to be that precise, it could be something like
    >> the UN geoscheme[0], i.e. the following:
    >>
    >> - Eastern Africa
    >> - Middle Africa
    >> - Northern Africa
    >> - Southern Africa
    >> - Western Africa
    >> - Caribbean
    >> - Central America
    >> - Northern America
    >> - South America
    >> - Central Asia
    >> - Eastern Asia
    >> - South-eastern Asia
    >> - Southern Asia
    >> - Western Asia
    >> - Eastern Europe
    >> - Northern Europe
    >> - Southern Europe
    >> - Western Europe
    >> - Australia and New Zealand
    >> - Melanesia
    >> - Micronesia
    >> - Polynesia
    >
    >> Optionally some regions like “North America” and “Eastern Europe” could
    >> be subdivided[1].  This gives us an approximation of where Emacs users are
    >> found, instead of what countries they might or might not have been born
    >> in.
    >
    > Nationality isn’t which country you’re born in, but the country you belong to
    > most.

    For someone like me this is a meaningless question, and I don't think I
    am alone here.  Again, what I am wondering is what the question's intent
    is.  Maybe I am missing something but finding out what the association
    is between Emacs usage/behaviour and residence seems more interesting
    than national identity.

It might also be that the entire question and anything related to it is
pointless to begin with...

> With regards to survey promotion, I’m thinking it would be good to mention this
> as widely as possible to try to reach a diverse range of respondents. If other
> people might have ideas on how to effectively share this survey around, that
> would be great.

It will probably be best to mention in the usual places (the mailing
lists, IRC, Emacs news, r*ddit, HN, image boards, etc.) with an explicit call
to share it among friends and colleagues that also use Emacs but perhaps
don't follow "recent events".

Anything beyond that will probably be a waste of time.

> All the best,
> Timothy



  reply	other threads:[~2022-10-02 16:06 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 14:51 Emacs Survey 2022 - design Timothy
2022-05-17 15:38 ` Visuwesh
2022-05-19 14:36   ` Timothy
2022-05-17 18:20 ` Stefan Monnier
2022-05-17 19:52   ` Tassilo Horn
2022-05-17 22:21     ` Stefan Monnier
2022-05-18  4:49       ` Tassilo Horn
2022-05-18 12:43         ` Stefan Monnier
2022-05-18 18:47           ` Philip Kaludercic
2022-05-19 14:39   ` Timothy
2022-05-17 18:59 ` Philip Kaludercic
2022-05-19 14:54   ` Timothy
2022-05-19 16:11     ` Philip Kaludercic
2022-05-20  8:11   ` sr
2022-05-20 23:53     ` Philip Kaludercic
2022-05-17 19:43 ` Juri Linkov
2022-05-19 15:13   ` Timothy
2022-05-17 22:16 ` Howard Melman
2022-05-17 22:21 ` Howard Melman
2022-05-17 22:44 ` Will Mengarini
2022-05-17 23:00   ` Stefan Monnier
2022-05-18  0:15     ` Corwin Brust
2022-05-18  7:13       ` Philip Kaludercic
2022-05-19 15:51         ` Timothy
2022-05-19 15:54     ` Timothy
2022-05-19 17:37       ` Stefan Monnier
2022-10-10 17:48         ` Gregor Zattler
2022-05-18  4:39   ` Visuwesh
2022-05-19 15:48     ` Timothy
2022-05-19 15:18   ` Timothy
2022-05-18 11:19 ` Jonas Bernoulli
2022-05-18 18:46   ` Philip Kaludercic
2022-05-19 15:30   ` Timothy
2022-05-18 12:47 ` Jostein Kjønigsen
2022-05-19 15:26   ` Timothy
2022-05-18 22:19 ` Richard Stallman
2022-05-19 15:38   ` Timothy
2022-05-21 22:46     ` Richard Stallman
2022-05-18 22:20 ` Richard Stallman
2022-05-19 15:41   ` Timothy
2022-05-21 22:46     ` Richard Stallman
2022-05-22 11:32       ` Akib Azmain Turja
2022-05-22 12:03         ` Philip Kaludercic
2022-05-19  5:22 ` Mike Kupfer
2022-05-19 15:44   ` Timothy
2022-05-19 16:17     ` Mike Kupfer
2022-05-19 16:01 ` Benjamin Riefenstahl
2022-05-23  7:16 ` Emacs Survey 2022 - 1st question Jean Louis
2022-05-23 17:14   ` Timothy
2022-05-23  7:18 ` Emacs Survey 2022 - 2nd question Jean Louis
2022-05-23 17:17   ` Timothy
2022-05-24  0:21     ` Richard Stallman
2022-05-23  7:19 ` Emacs Survey 2022 - 3rd question Jean Louis
2022-05-23  7:24 ` Emacs Survey 2022 - which editor question Jean Louis
2022-05-23  8:04   ` Philip Kaludercic
2022-05-23  8:14     ` Jean Louis
2022-05-23 17:29   ` Timothy
2022-05-23  7:27 ` Emacs Survey 2022 - how you were introduced to Emacs Jean Louis
2022-05-23 17:18   ` Timothy
2022-05-23 18:43     ` Philip Kaludercic
2022-05-23 18:54       ` Timothy
2022-05-23  7:31 ` Emacs Survey 2022 - what features? Jean Louis
2022-05-23 17:19   ` Timothy
2022-05-23  7:36 ` Emacs Survey 2022 - email client Jean Louis
2022-05-23 17:23   ` Timothy
2022-05-23  7:40 ` Emacs Survey 2022 - nationality Jean Louis
2022-05-23  8:35   ` Ihor Radchenko
2022-05-23  7:43 ` Emacs Survey 2022 - industry Jean Louis
2022-05-23 17:25   ` Timothy
2022-05-23 20:36     ` John ff
2022-05-23  7:45 ` Emacs Survey 2022 - how did you fid out about survey Jean Louis
2022-05-23 17:28   ` Timothy
2022-05-23 18:40     ` Philip Kaludercic
2022-05-23  8:46 ` Emacs Survey 2022 - design Lars Ingebrigtsen
2022-10-02  8:30 ` Timothy
2022-10-02 16:06   ` Philip Kaludercic [this message]
2022-10-04  1:00     ` Richard Stallman
2022-10-04  7:00       ` Philip Kaludercic
2022-10-04  7:53         ` Richard Stallman
2022-10-04  8:00   ` Akib Azmain Turja
2022-10-04  8:38     ` Po Lu
2022-10-04  9:37     ` Philip Kaludercic
2022-10-05 16:48   ` Philip Kaludercic
  -- strict thread matches above, loose matches on Subject: below --
2022-05-22  8:38 Johan Myréen
2022-05-22 13:03 ` Stefan Monnier

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=87edvq2osi.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=tec@tecosaur.net \
    /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).