Re: Running a Guix User and Contributor survey

[Steve George <steve@futurile.net>]

Hi Denis,

Thanks for reading through it.

On  5 Nov, Denis 'GNUtoo' Carikli wrote:
> On Wed, 30 Oct 2024 12:03:26 +0000
> Steve George <steve@futurile.net> wrote:
> Here's some feedback on the proposal below.
> 
> > # Audience
> > The audience for this survey are all Guix users and contributors
> > [^1]. This means:
> > 
> > - Guix user: anyone who uses all or part of Guix, whether as their
> > operating system or hosted on another GNU/Linux distro.
> > - Guix contributor: anyone who sends changes (patches) to the
> > project. This includes code changes, but also other improvements
> > including documentation, design and translation. This is an extensive
> > group beyond those with commit rights.
> > - Guix community: the totality of both groups.
> Most Guix contributors are also users, so this may need to be reflected
> in some ways.
(...)

This is a difficult to do in a nice way without a wall of text. It's a key question so I've added help text:

For this question choose **User** if you use Guix: this includes community members who promote the project and take part in the support channels. Choose **Contributor** if you also sent patches of any form: whether those are code, documentation, translations or anything else. Choose **Committer** if you have access to the Guix Git repository.

(...)
> > **Q1. How knowledgeable a Linux user are you?**
> GNU/Linux would probably be better given the audience here.
> 
> >   - an official GNU FSF (Free Software Foundation) project
> The distribution is certified by the FSF but it's a GNU package. The
> FSF doesn't maintain the Guix package though.
>
> So maybe this could be better:
> > **Q5. Why were you initially interested in Guix?**
> [...]
> > An FSF certified 100% free software distribution.
> 

I think these are equivalent to be honest, but happy to change it.

> I'm also unsure if it should be added to the list or not but being able
> to install software on top of another distribution is a common use case
> so that might be a reason to use it. And this can be done for a wide
> variety of reasons (ship software to users, use it in some QA process,
> etc).
> 
> I'm also aware that this option is also included in a question on how
> we use Guix.
(...)

Added it, since that's certainly the reason I started using Guix. This question is trying explore the "initial interest" so it's reasonable to have a variety of things.

Steve / Futurile