all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: indieterminacy <indieterminacy@libre.brussels>
To: Wilko Meyer <w@wmeyer.eu>
Cc: Steve George <steve@futurile.net>, guix-devel@gnu.org
Subject: Re: Running a Guix User and Contributor survey
Date: Fri, 01 Nov 2024 14:14:21 +0000	[thread overview]
Message-ID: <9edc1c9f7d37e11986f4a59fb3921ae5@libre.brussels> (raw)
In-Reply-To: <87zfmjcot8.fsf@wmeyer.eu>

On 2024-11-01 08:59, Wilko Meyer wrote:
> Hi Steve,
> 
> Steve George <steve@futurile.net> writes:
> 
>> 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.
> 
> Thanks for putting work into this, that's awesome! In terms of general
> feedback: There was a general discussion on surveys[0] a year ago, I'd
> like to highlight this mail[1] by Katherine in particular, as it
> contains excellent points on survey/questionnaire design and good
> practices.
> 
> Regarding your proposed questionnaire: I think that it would benefit
> from asking about the level of Guile proficiency/if there's
> prior-experience with lisp family languages/if people learned Guile
> because of Guix.
> 
>> * 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.
> 
> It could be feasible to categorize questions into two boxes:
> 
> - Questions we want to track over time as we want to track how 
> responses
>   change over the years, that have to be iterated yearly.
> - Questions we want to ask once/every few years, as we want to work 
> with
>   a snapshot in time instead of longterm tracking answers in short
>   iterations.
> 
> and then have a annual/biennial survey, always asking all questions 
> from
> the first box, and then split-up questions from the second box
> throughout the years.
> 

If it is to be a biennial survey it may be useful to allow people to 
upload previous questionaires,
so that they can be parsed for populating new survey responses.

I can provide a parser prior to the subsequent polling in TXR if that 
helps.

>> * If anyone has skills/experience in analysing results and would like 
>> to get
>> involved I would love help.
> 
> Don't know yet what my timebudget will look like when the results are
> in, but generally I'd be available for this (if time permits)!
> 
> [0]: 
> https://lists.gnu.org/archive/html/guix-devel/2023-09/msg00402.html
> [1]: 
> https://lists.gnu.org/archive/html/guix-devel/2023-09/msg00481.html


  reply	other threads:[~2024-11-01 17:02 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=9edc1c9f7d37e11986f4a59fb3921ae5@libre.brussels \
    --to=indieterminacy@libre.brussels \
    --cc=guix-devel@gnu.org \
    --cc=steve@futurile.net \
    --cc=w@wmeyer.eu \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.