all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: [ANN] The 2022 Emacs User Survey is now open!
Date: Tue, 25 Oct 2022 10:26:49 +1100	[thread overview]
Message-ID: <865yg8kcqp.fsf@gmail.com> (raw)
In-Reply-To: <874jvtmrjv.fsf@tecosaur.net>


I agree with Po. The question "When you discover a new package that
looks interesting, what do you do next?" needs a do nothing or perhaps
"Wait until I actually need it before trying it out". I see many
'interesting' packages, but most of them I don't try or use because
despite being interesting, they add no value to what I actually do.

More generally, I feel the questions about packages have a slight bias
towards a behaviour which I frequently see, but feel is often
misguided. That is, to madly install lots of packages, most of which you
never use (a behaviour common in other systems which use a package
system to extend functionality). I am on a number of lists/forums where
people often want support/help with Emacs. A very common resolution for
issues they are encountering is to remove lots of unused and unnecessary
packages. Frequently, once we cut down to only the packages they
actually use, problems they have encountered go away. 

My use case is that while I may note an interesting looking package in
my Emacs notes file, I am unlikely to ever install it unless it
addresses some issue I am running into. I tend not to actually monitor
the release of new packages. Instead, I will look for an appropriate
package when I identify some need or weakness in current workflow. It
isn't easy to express this use case in the survey. 

Timothy <tec@tecosaur.net> writes:

> Hi All,
>
> I’m thrilled to announce that the Emacs User Survey 2022 is now open to
> responses. It is my hope that this may help emacs-devel, Emacs package
> maintainers, and the wider Emacs community, develop a better understanding of
> how people experience Emacs on a day-to-day basis.
>
> <https://emacssurvey.org/>
>
> The survey will be open from October 24th to November 30th.
>
> This time there are /no/ non-free Javascript or user-tracking caveats as this
> features a bespoke survey framework written from scratch for the Emacs User
> Survey to support a pure HTML-forms + CSS approach with server-side rendering
> 🎉.
>
> See the [FAQ] for more information on the survey itself.
>
> It would be fantastic for this to be shared as far and wide as possible, to get
> responses from a large swathe of the community. If you can share this with Emacs
> communities you are a part of, as well as any friends or colleagues that use
> Emacs, that would be much appreciated.
>
> We can look forward to a discussion of the (preliminary) results in EmacsConf:
> <https://emacsconf.org/2022/talks/survey/>.
>
> All the best,
> Timothy
>
>
> [FAQ] <https://emacssurvey.org/faq.html>




  parent reply	other threads:[~2022-10-24 23:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 10:27 [ANN] The 2022 Emacs User Survey is now open! Timothy
2022-10-24 13:25 ` Po Lu
2022-10-24 14:40 ` Akib Azmain Turja
2022-10-24 14:48   ` Timothy
2022-10-25 11:29     ` Akib Azmain Turja
2022-10-24 16:05 ` Philip Kaludercic
2022-10-24 23:26 ` Tim Cross [this message]
2022-10-25  1:30   ` [External] : " Drew Adams
  -- strict thread matches above, loose matches on Subject: below --
2022-10-24 10:42 Timothy
2022-10-24 11:32 ` Russell Adams
2022-10-24 11:37 ` Jean Louis
2022-10-26  6:18 ` Christopher M. Miles
     [not found] ` <6358d205.050a0220.d906e.8b76SMTPIN_ADDED_BROKEN@mx.google.com>
2022-10-26  6:23   ` Samuel Wales
2022-10-24 11:15 Payas Relekar

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

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

  git send-email \
    --in-reply-to=865yg8kcqp.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-devel@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.