From: Timothy <tecosaur@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs Survey 2022 - design
Date: Thu, 19 May 2022 22:39:28 +0800 [thread overview]
Message-ID: <87bkvtbmkk.fsf@gmail.com> (raw)
In-Reply-To: <jwvo7zw82mk.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 4206 bytes --]
Hi Stefan,
Thanks for all the feedback!
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> validators = v -> if v < 0
>
> Could also just be a wrap around.
Perhaps, I’m inclined to leave it as “yelling at the user for doing something
silly” though.
>> MultiSelect(:emacs_mode,
>
> You can use the daemon with GUI frames or with text frames (or both), so
> the 3 choices aren’t mutually exclusive.
“MultiSelect” corresponds to a set of checkboxes, any number of which can be
selected (as opposed to “RadioSelect”). So, these options aren’t mutually
exclusive :)
>> MultiSelect(:languages,
>
> ELisp is strangely missing here.
How did I miss that!? Added.
>> SurveyPart(“First time questions”,
>> “All of these questions are <i>optional</i>. Answer these if you’re
>> doing the survey for the first time.”,
>
> I think “taking” is the better verb here instead of “doing”, tho
> hopefully some native anglophone can confirm.
That sounds better to me.
>> SurveyPart(“Packages”,
>
> `use-package` looks out of place, since I don’t think it offers any
> facilities to download/install/update/uninstall packages.
This seems to have been well-discussed in replies. I’m inclined to leave it in
for now.
>> MultiSelect(:package_repositories,
>
> NonGNU ELPA?
Added.
>> MultiSelect(:theme, # people can use a light and dark theme
>
> The default theme is actually 2 themes (a dark one and a light one), so
> it would make more sense to split it into two (or otherwise to merge
> modus-operandi and modus-vivendi as well as solarized and solarized-dark).
Default has been split into -light and -dark variants.
>> RadioSelect(:melpa_contribution,
>> “Have you ever contributed to a Melpa package?”,
>> [“No”, “Occasionaly”, “Frequently”]),
>
> [ BTW, last I checked it’s spelled “MELPA” and not “Melpa”. Don’t know
> if the MELPA guys care about the difference, tho. ]
>
> Not sure what the question means, really: you can’t contribute via
> MELPA, and most packages are on MELPA, so if you contributed to an ELisp
> package, that contribution probably found its way to MELPA even if you
> never heard of it.
Mmm. I’ve changed this to the more general “contributed to an Emacs package?”.
> To a large extent the same holds for GNU ELPA, so maybe the distinction
> between “contributed to MELPA packages” vs “contributed to GNU ELPA
> packages” just doesn’t make much sense.
I think Emacs/ELPA are a little different with the ML process and FSF approval.
> Without knowing what you’re hoping to do with the result of that
> question it’s hard to know what to do with it, but maybe you’re rather
> interested to distinguish contributions via `M-x report-emacs-bug` or
> emacs-devel from contributions via things like merge requests on
> some forge?
My thinking here is that it could be interesting to see what the contributed
with/without using a mailing list and getting FSF approval ratio (i.e.
Emacs/ELPA) looks like, and particularly any shifts in it over time.
>> RadioSelect(:has_donated,
>> “Have you ever contributed financially to Emacs development (via the FSF)”,
>
> I think FSF membership does contribute (to a very small extent), so
> maybe you want to clarify whether you’d count this as a valid
> contribution or whether you’re thinking of more
> significant/targeted contributions?
The idea here is looking at financial contributions to Emacs, but I’m not sure
what would make the most sense. Perhaps it would be worth asking about donations
to package maintainers? I’d appreciate hearing other people’s thoughts on this.
>> “Asosociate’s Degree” => “Asosociates”,
>
> I don’t know that one. I’m tempted to say it’s a typo for “Associates”?
Neither do I, but apparently it’s a 2 year degree usually from a community
college, common in the US.
Yep, there’s a typo there. Fixed.
All the best,
Timothy
next prev parent reply other threads:[~2022-05-19 14:39 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 [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
2022-05-22 8:38 Johan Myréen
2022-05-22 13:03 ` Stefan Monnier
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=87bkvtbmkk.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).