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 <emacs-devel@gnu.org>
Subject: Re: [ANN] The 2022 Emacs User Survey is now open!
Date: Mon, 24 Oct 2022 16:05:54 +0000	[thread overview]
Message-ID: <874jvt436l.fsf@posteo.net> (raw)
In-Reply-To: <874jvtmrjv.fsf@tecosaur.net> (Timothy's message of "Mon, 24 Oct 2022 18:27:26 +0800")

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/>

Great!

I don't know if it is too late, but it seems that you recently copied a
few questions from the 2020 survey, right?  I assume so because I
couldn't find "Common Lisp" in the programming language list (again).
Is it too late to add it, or are you satisfied with people just adding
Common Lisp manually?

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

1+

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

I will do my best to spread the word among friends and colleagues.

> 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 16:05 UTC|newest]

Thread overview: 8+ 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 [this message]
2022-10-24 23:26 ` Tim Cross
2022-10-25  1:30   ` [External] : " Drew Adams

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=874jvt436l.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).