Re: Emacs Survey 2022 - design

[Philip Kaludercic <philipk@posteo.net>]

Jonas Bernoulli <jonas@bernoul.li> writes:

>> ** Do you have any general feedback on the survey?
>
> That's it?  That wasn't many questions.
>
> 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
>   alternatives?
> - 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>.

Will is be possible to filter out questions, depending on previous
answers?  I don't think the average user is interested in questions
about how they maintain Elisp code.