From: Luis Felipe <sirgazil@zoho.com>
To: Steve George <steve@futurile.net>, guix-devel@gnu.org
Subject: Re: Running a Guix User and Contributor survey
Date: Wed, 30 Oct 2024 17:08:52 +0000 [thread overview]
Message-ID: <83b2fb02-f171-4d46-b1f0-9ffccf90d9a5@zoho.com> (raw)
In-Reply-To: <h5cojlw6y2pmq24eh7aakvvnhm3gjttfh7nzi5erb7rzdgfib2@rj4m6ogu6ysm>
[-- Attachment #1.1.1: Type: text/plain, Size: 2617 bytes --]
Hi Steve,
On 30/10/24 12:03, Steve George wrote:
> Hi,
>
> I've designed a 'Guix User and Contributor Survey' which I'd like to run to
> explore what users love about Guix, and how contributors interact
> with the project. I would love feedback on it.
>
> The rationale for a survey is that it's a way to build up an understanding of
> our users and contributors which can inform our thoughts and decisions. As a
> project that's focused on user-freedom we don't use telemetry or have the
> resources to run professional user research. A survey provides a broad picture
> across our community, it standardises the questions that are asked and can
> show trends across our community. The proposal links to surveys by projects
> like Nix and Fedora which I've used for inspiration.
I gave it a first look, and I want to see the results already :)
> Informed by those surveys, and my own interations with Guix users I've selected
> questions that delve into how people are adopting and using Guix. The second
> part explores how people contribute to Guix and their interactions with the
> project. Please see the design document for the various considerations and
> constraints.
>
> Some specific ways you can help are:
>
> * 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.
> * 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.
That's all for now.
Looking forward to survey publication :)
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2881 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
prev parent reply other threads:[~2024-10-30 17:10 UTC|newest]
Thread overview: 2+ 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 [this message]
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=83b2fb02-f171-4d46-b1f0-9ffccf90d9a5@zoho.com \
--to=sirgazil@zoho.com \
--cc=guix-devel@gnu.org \
--cc=steve@futurile.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/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).