unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Steve George <steve@futurile.net>
To: Luis Felipe <sirgazil@zoho.com>
Cc: guix-devel@gnu.org
Subject: Re: Running a Guix User and Contributor survey
Date: Thu, 31 Oct 2024 14:56:06 +0000	[thread overview]
Message-ID: <id4dpkzumc254y7qv7ep6xinxuabrkgrjxfol6moapa2qwz2zd@wkehltex7xvz> (raw)
In-Reply-To: <83b2fb02-f171-4d46-b1f0-9ffccf90d9a5@zoho.com>

On 30 Oct, Luis Felipe wrote:
(...)
> On 30/10/24 12:03, Steve George wrote:
(...) 
> I gave it a first look, and I want to see the results already :)

Thank-you, appreciate you going through it.

(...)
> > * The tricky part of running a survey is keeping it to a reasonable length, you
> > quickly find there's lots you'd love to know, but the balancing factor is the
> > more questions someone has to answer the lower the completion rate! Ideas on
> > how to shorten the design while keeping the same areas of enquiry would be
> > welcome.
> 
> Personally, I think it is a bit long. Would it make sense to make it two
> surveys instead, one for users and one for contributors?
> 
> I'm thinking that if it is perceived as lengthy, people might omit the
> free-form questions at the end or be too tired to express themselves as
> they'd like to.
(...)

Yeah, I have the same concern. I'm going to have a look at it when it's
laid-up as a questionnaire and see how it seems for filling it out. I'm not
sure about splitting it up - I'll give it some serious thought though as your
reaction is what I was worrying about.

> > * I'm sure there are alternative word options that might be clearer, along with
> > the inevitable typos: either a PR (it's on Codeberg where anyone can create an
> > account) or a patch would be welcome.
> 
> I only noticed one typo:
> 
> + decison making → decision making
> 
> And two trifles⸮:
> 
> 1. "Guixers" used to refer to "Guix denizens". I would omit it because, to
> my knowledge, the community hasn't decided on an English demonym yet (/me
> runs and takes cover).
> 2. Use of "Linux" in the first and other questions to refer to GNU/Linux
> distributions in general. I'd use the latter, to follow the same convention
> used in Guix documentation.

Thanks for these.

Futurile / Steve




  reply	other threads:[~2024-10-31 14:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-30 12:03 Running a Guix User and Contributor survey Steve George
2024-10-30 17:08 ` Luis Felipe
2024-10-31 14:56   ` Steve George [this message]
2024-10-31 15:44 ` Ekaitz Zarraga
2024-11-01 20:21   ` Steve George
2024-11-05  1:01   ` Denis 'GNUtoo' Carikli
2024-11-01  8:59 ` Wilko Meyer
2024-11-01 14:14   ` indieterminacy
2024-11-01 20:40   ` Steve George
2024-11-04 22:04 ` Ludovic Courtès
2024-11-05  1:22 ` Denis 'GNUtoo' Carikli
2024-11-08 10:30   ` Steve George

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=id4dpkzumc254y7qv7ep6xinxuabrkgrjxfol6moapa2qwz2zd@wkehltex7xvz \
    --to=steve@futurile.net \
    --cc=guix-devel@gnu.org \
    --cc=sirgazil@zoho.com \
    /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/guix.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).