From: Timothy <email@example.com>
To: Jonas Bernoulli <firstname.lastname@example.org>
Subject: Re: Emacs Survey 2022 - design
Date: Thu, 19 May 2022 23:30:28 +0800 [thread overview]
Message-ID: <email@example.com> (raw)
Jonas Bernoulli <firstname.lastname@example.org> writes:
>> I’m pushing for a 2022 Emacs survey.
> Always fun. Thanks!
I'm looking forward to seeing where this goes :)
>> ** How do you manage third-party packages?
> Please include borg (https://github.com/emacscollective/borg). It may
> not have many users but then again, it may. Only one way to find out.
The "other" boxes are actually text fields in the survey, so people can
actually just type "borg" in should they use it :)
>> - [ ] Frequently
>> - [ ] Rarely
>> - [ ] Never
> That's like those scientific studies that only offer four levels of X to
> choose from, except here it's only three choices here. What about "All
> the time", to get at least to the level of detail, that that Covid study
> I took part in, had? Maybe also add "Occasionally" in the middle; the
> neutral option that is so often missing?
> [Is anyone aware of a study about whether leaving out a neural option
> leads to more polarized results? I.e., is mildly-pro+mildly-contra ~=
> mildly-pro+neutral+mildly-contra, or are respondents encouraged to
> pick the extremes (e.g., because both mild variants are seen as neutral
> in the absence of a fully neutral choice)?]
This is a very good point, thanks for raising it! How about:
Frequently, Often, Sometimes, Rarely, Never ?
>> ** Do you have any general feedback on the survey?
> That's it? That wasn't many questions.
I'm inclined to be conservative to maximise value/respondent time, but I
think there's plenty of room for good suggestions. There's good reason
why I called this a draft :)
> They would need some work, but here are some I would be interested in:
> - How do you learn about new packages?
> - Do you try out new interesting packages immediately, or wait for them
> to mature?
> - Do you sometimes discover old package and use them instead of newer
> - Do you research established alternatives when a new shiny package
> comes along?
> - Do you install the packages that you maintain yourself using package.el?
> (As opposed to manually adding the appropriate directory to the load-path.)
> - Do you publish your own packages on an *ELPA as soon as they are
> usable, or do let them mature a bit first? (Why the former?)
> - How often do you contribute new features to the packages you use?
> - How often do you contribute bugfixes to the packages you use?
> - How often do you ask the maintainers of the packages you use for help?
> - Where do you request help with packages that are part of GNU Emacs?
> - Where do you request help with packages that are not part of GNU Emacs?
> - If you use a starter-kit, who do you usually ask for help first; the
> starter-kit maintainers, the package maintainers, the wider community?
> - What do you do if your feature request or contribution is rejected?
> - What documentation do you wish package authors would more often
> provide?  Comparison with alternatives  Tutorials  Design
> rational  Info manual  Screenshots  Videos  Concise
> introduction  ... [ ] <input field>.
I'll get a second opinion on this list, but I think a bunch of these
questions look like very promising candidates for inclusion.
Thanks for your thoughts!
next prev parent reply other threads:[~2022-05-19 15:30 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 [this message]
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
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
2022-05-22 8:38 Johan Myréen
2022-05-22 13:03 ` Stefan Monnier
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:
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 \
* 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
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).