unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Steve George <steve@futurile.net>
To: guix-devel@gnu.org
Subject: Running a Guix User and Contributor survey
Date: Wed, 30 Oct 2024 12:03:26 +0000	[thread overview]
Message-ID: <h5cojlw6y2pmq24eh7aakvvnhm3gjttfh7nzi5erb7rzdgfib2@rj4m6ogu6ysm> (raw)


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.

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.

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

* If anyone has skills/experience in analysing results and would like to get 
involved I would love help.

Depending on the response/feedback I'll then move into implementing and running it. All the details here:

https://codeberg.org/futurile/guix-survey/src/branch/main/guix-user-contributor-survey-proposal.md

Thanks,

Steve / Futurile


             reply	other threads:[~2024-10-30 12:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-30 12:03 Steve George [this message]
2024-10-30 17:08 ` Running a Guix User and Contributor survey Luis Felipe
2024-10-31 14:56   ` Steve George
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=h5cojlw6y2pmq24eh7aakvvnhm3gjttfh7nzi5erb7rzdgfib2@rj4m6ogu6ysm \
    --to=steve@futurile.net \
    --cc=guix-devel@gnu.org \
    /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).