unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Steve George <steve@futurile.net>
To: Ekaitz Zarraga <ekaitz@elenq.tech>
Cc: guix-devel@gnu.org
Subject: Re: Running a Guix User and Contributor survey
Date: Fri, 1 Nov 2024 20:21:59 +0000	[thread overview]
Message-ID: <3slagec6ytiqydgpld45vfomdarwzc65uhjfzzpfjcjbtjzllb@gvgu262l5aem> (raw)
In-Reply-To: <fa159da2-6612-40ba-a47f-834e74eac251@elenq.tech>

Hi Ekaitz,

Thanks for going through it!

On 31 Oct, Ekaitz Zarraga wrote:
> Hi Steve,
> 
> I don't think the survey is very long.
> 
> We could try to answer and then share it with a note on the top that says
> how long it takes, so people can decide when to fill it.
(...)

Agreed, I've added some intro text. And when I've set it up I'll run through it and make sure there's text saying how long it should take.

> Also I like when people have space to answer, because that motivates
> insightful responses. It probably goes against the theory on how to make a
> good survey but I believe it could be interesting to leave the space for
> complex thoughts. I think complexity of thoughts is often ignored and it's
> important to take good decisions.
> 
> Some specifics:
> 
> To the question about why Guix (Q5) I would add some flavor of "Free
> Software".
(...)

Added, thanks for suggesting it.

> About if people is paid for working on Guix (Q22), I think there's something
> lost there even if the second answer can make it fit: people that use Guix
> and they are not paid for contributing in Guix but fixing/improving Guix
> sometimes is some consequence of their job. I mean, they are paid for it,
> but their job is not to improve Guix, but something else. It's tangential.
(...)

Agreed, that we're not fully exploring this for now. For this time I only want 
to give it one question. Lets see what we get back and we can decide if it
should have further depth in future.

> About the financial support (Q29) maybe it's possible to ask how much people
> is open to give to Guix per month.
(...)

Honestly, I think the way to find this out is to "do it". Something to explore
as a follow-up to the other thread maybe!

> Those are my two cents. In general, I like the survey.
> 
> It's probably ok just to launch it than to try to make it perfect the first
> time. We could run one per year and improve them according to the answers we
> get. Those that don't really give us interesting information we could just
> ignore.
(...)

Agreed, it's better to do something, lets see if it gets a response and people fill it in.

> Have you thought about what platform use?
> 
> I think we could do with Framasoft:
> https://framasoft.frama.io/framaforms/en/
(...)

I wasn't aware of this platform, I'll add it to the list.

Thanks for the input!

Steve / Futurile


  reply	other threads:[~2024-11-01 20:23 UTC|newest]

Thread overview: 8+ 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 [this message]
2024-11-01  8:59 ` Wilko Meyer
2024-11-01 14:14   ` indieterminacy
2024-11-01 20:40   ` 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=3slagec6ytiqydgpld45vfomdarwzc65uhjfzzpfjcjbtjzllb@gvgu262l5aem \
    --to=steve@futurile.net \
    --cc=ekaitz@elenq.tech \
    --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).