[ANN] The 2022 Emacs User Survey is now open!

[ANN] The 2022 Emacs User Survey is now open!

[Timothy]

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

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>

Re: [ANN] The 2022 Emacs User Survey is now open!

[Po Lu]

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>

Thanks.  While filling out the survey, I noticed something missing:

When you discover a new package that looks interesting, what do you do next?
Install and try it immediately
Research alternatives
Wait for it to mature
Wait till I see other people in the community using it

This seems to be missing an option for "I don't do anything."

Re: [ANN] The 2022 Emacs User Survey is now open!

[Akib Azmain Turja]

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

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

I just completed the survey, and it was great.  But I couldn't see my
results in any of txt, org or json: they say everything is missing.

-- 
Akib Azmain Turja

Find me on Mastodon at @akib@hostux.social, and on Codeberg (user
"akib").

This message is signed by me with my GnuPG key.  Its fingerprint is:

    7001 8CE5 819F 17A3 BBA6  66AF E74F 0EFA 922A E7F5

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

Re: [ANN] The 2022 Emacs User Survey is now open!

[Timothy]

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

Hi Akib,

> I just completed the survey, and it was great.  But I couldn’t see my
> results in any of txt, org or json: they say everything is missing.

There seems to be an issue that has decided to raise its head during production
😓.

For some reason, certain responses display as though some or all of the answers
are “missing” even when an answer was given. I have investigated a number of
cases like this, and in every one the data has been correctly recorded in the
database, but for some reason it is displayed/exported incorrectly.

I will look into this more later, but for now it appears as though no data is
lost, even though it may appear concerning.

All the best,
Timothy

Re: [ANN] The 2022 Emacs User Survey is now open!

[Akib Azmain Turja]

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

Timothy <contact@tecosaur.net> writes:

> Hi Akib,
>
>> I just completed the survey, and it was great.  But I couldn’t see my
>> results in any of txt, org or json: they say everything is missing.
>
> There seems to be an issue that has decided to raise its head during production
> 😓.
>
> For some reason, certain responses display as though some or all of the answers
> are “missing” even when an answer was given. I have investigated a number of
> cases like this, and in every one the data has been correctly recorded in the
> database, but for some reason it is displayed/exported incorrectly.
>
> I will look into this more later, but for now it appears as though no data is
> lost, even though it may appear concerning.
>
> All the best,
> Timothy
>

Thanks for the quick response.  (Though I couldn't reply, thanks to the
connectivity problems and power outage due to the cyclone here.)

I still have the survey ID.  Will it help?  If yes, I'll send it to you
off-list.

FYI I used IceCat on GNU Guix with LibreJS turned on, and it probably
blocked some JavaScript.

-- 
Akib Azmain Turja

Find me on Mastodon at @akib@hostux.social, and on Codeberg (user
"akib").

This message is signed by me with my GnuPG key.  Its fingerprint is:

    7001 8CE5 819F 17A3 BBA6  66AF E74F 0EFA 922A E7F5

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

Re: [ANN] The 2022 Emacs User Survey is now open!

[Philip Kaludercic]

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>

Re: [ANN] The 2022 Emacs User Survey is now open!

[Tim Cross]

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>

RE: [External] : Re: [ANN] The 2022 Emacs User Survey is now open!

[Drew Adams]

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

+1