unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jostein Kjønigsen" <jostein@secure.kjonigsen.net>
To: Timothy <tecosaur@gmail.com>, emacs-devel@gnu.org
Subject: Re: Emacs Survey 2022 - design
Date: Wed, 18 May 2022 14:47:08 +0200	[thread overview]
Message-ID: <d0409073-3373-46c5-9965-b155601ad7a3@secure.kjonigsen.net> (raw)
In-Reply-To: <87ee0sb3by.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2084 bytes --]

On 17.05.2022 16:51, Timothy wrote:
>
> Hello,
>
> I’ve recently been chatting with Adrien Brochard (who ran the 2020 
> Emacs survey), and I’m pushing for a 2022 Emacs survey.
>
> Even with detailed telemetry (urgh) it can be hard to understand the 
> range of experiences and opinions users have. As such, particularly 
> once we have past surveys to reference and some consistent questions, 
> I see quite a bit of value in helping:
>
>  1. Emacs developers,
>  2. Emacs package developers/maintainers,
>  3. The Emacs community itself
>
> better understand the Emacs community.
>
> Of course, this being a fiercely FOSS community, the situation with 
> survey platforms leaves quite a bit to be desired. To resolve this 
> issue, I spent some time last year writing a 100% FOSS, survey 
> framework <https://github.com/tecosaur/emacs-survey> which is 
> completely functional without any JS. I have attached some screenshots 
> of it to this email.
>
> It would be good to maximise the utility of the survey to the three 
> groups mentioned earlier. In this vein I hope some of you, 
> emacs-devel, would be willing to provide some feedback on the survey :)
>
> Attached you may find the current draft survey questions, both as 
> survey-questions.org file and the configuration file used by my survey 
> framework, survey.jl. If you’d like, you can even try running the 
> survey locally.
>
> Lastly, if any of you would like to chat about this over IRC you can 
> find me as “tecosaur” on libera.chat, and @tecosaur:matrix.org over on 
> Matrix.
>
> All the best,
> *Timothy*
>

A few comments:

- How were you introduced to Emacs? "Emacs recommended by collegue" is 
not an option, despite using Emacs for work being an option.
- Survey seems programmer-centric. What about people using Emacs for 
non-programming purposes? I.e. as a text-editor?
- Which Industry do you work in? Could use a creative/writing? 
Media/publishing? Etc.

My 2 cents

-- 
*Jostein Kjønigsen*
jostein.kjønigsen.no <https://jostein.kjønigsen.no>
jostein@kjonigsen.net - jostein@gmail.com

[-- Attachment #2: Type: text/html, Size: 8043 bytes --]

  parent reply	other threads:[~2022-05-18 12:47 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 [this message]
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
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=d0409073-3373-46c5-9965-b155601ad7a3@secure.kjonigsen.net \
    --to=jostein@secure.kjonigsen.net \
    --cc=emacs-devel@gnu.org \
    --cc=tecosaur@gmail.com \
    /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).