unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Wilko Meyer <w@wmeyer.eu>, guix-devel@gnu.org
Subject: Re: Guix Survey (follow up on "How can we decrease the cognitive overhead for contributors?")
Date: Wed, 20 Sep 2023 11:37:49 +0200	[thread overview]
Message-ID: <875y459ocy.fsf@gmail.com> (raw)
In-Reply-To: <87y1h6qjxl.fsf@wmeyer.eu>

Hi,

Really cool!  Thank you.

On Sat, 16 Sep 2023 at 14:59, Wilko Meyer <w@wmeyer.eu> wrote:

> I identified a few key themes that could be useful for a guix user
> survey as well. I plan on doing a more extensive summary on this later
> this weekend if my time allows it, for now a loose collection of
> ideas/list of what, in my subjective opinion, stood out and what most
> surveys had in common should do to hopefully get a discussion on this
> started:
>
> - the emacs user survey specifically asked for elisp profiency; mapping
>   out the Guile profiency of guixes community could be feasible.
> - fennel as well as emacs had questions on which programming languages
>   their community uses; in the regards on recent discussions on
>   guix-devel on developer ecosystems[4] this could help to identify if
>   there are any shortcomings in providing importers/packages for certain
>   languages that may be used by guix users.
> - the nix survey specifically asked for the environments and context nix
>   is being used in; it'd be interesting to see where and for what
>   purpose people are using Guix.
> - most surveys had, some more some less extensive, demographic
>   questions and questions mapping out how many years people have been
>   programming.

I would add the questions as:

 + the kind of contributions: patches, translation, bug report,
 discussions on guix-devel or help-guix, else

 + the number of contributions using some ranges 1, [2-9], [10-100], 100+

 + channels of communication: IRC, guix-devel, help-guix, else (Reddit,
 etc.)

 + contribution to other free software (patches, translation, bug
 report)

 + editor of choice (as the survey from Haskell [1])

 + and maybe some other questions from [1] :-)

WDYT?

1: https://taylor.fausak.me/2022/11/18/haskell-survey-results/#s3q1

Cheers,
simon


  parent reply	other threads:[~2023-09-20 15:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-16 12:59 Guix Survey (follow up on "How can we decrease the cognitive overhead for contributors?") Wilko Meyer
2023-09-17 17:55 ` MSavoritias
2023-09-18 12:02 ` Peter Pronai
2023-09-20  9:37 ` Simon Tournier [this message]
2023-09-20 21:51   ` Wilko Meyer
2023-09-21 17:23     ` Katherine Cox-Buday
2023-10-02 11:24       ` Wilko Meyer
2023-10-09 18:29         ` Katherine Cox-Buday
2023-10-12 14:43           ` Simon Tournier
2023-11-06 22:46           ` Wilko Meyer
2023-10-08 12:07 ` Tao Hansen
2023-10-09 13:47   ` Lucy Coleclough
2023-10-11  6:53   ` Kjartan Óli Águstsson

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=875y459ocy.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --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 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).