unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Steve George <steve@futurile.net>
To: 74291@debbugs.gnu.org
Subject: [bug#74291] [Website patch] Announcing the Guix user survey - blog post
Date: Sun, 10 Nov 2024 12:00:26 +0000	[thread overview]
Message-ID: <bb0f4c02-5107-4ef6-9268-4748eae0d156@futurile.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 315 bytes --]

Hi,

I've finished designing the Guix user and contributor survey that was 
discussed on guix-devel.

I've announced it on IRC as a 'soft launch' so that everyone can find 
whatever spelling mistakes I've made!

Attached is a blog post for the Guix blog. Can someone add it for me please?

Thanks,

Steve / Futurile

[-- Attachment #2: 20241110-user-contributor-survey.md --]
[-- Type: text/markdown, Size: 1777 bytes --]

title: Take the Guix User and Contributor Survey
slug: guix-user-contributor-survey-2024
date: 2024-11-10 10:01:00
author: Steve George
tags: Community
---

To understand the views of the Guix community we're running a survey that we'd
love **you** to take part in! The
[Guix User and Contributor Survey](https://guix.limesurvey.net/216541) is live
now, and should take about 10 minutes to fill out. Perfect for doing with a cup
of tea and a biscuit!

The Guix project continues to grow and change, with new contributors and users
joining our community. We decided to run this survey as it's the best way to
gather good quality feedback across the widest cross-section of the community.
Of course, there's lots of interesting topics a survey could ask about! We
decided to focus on how Guix is used, and how contributors take part in the
project.

The survey is being run on
[LimeSurvey](https://en.wikipedia.org/wiki/LimeSurvey) which is a Free Software
project and has been used by many other projects for similar surveys. The
survey's hosted on the [LimeSurvey SaaS](https://www.limesurvey.org/) so that we
don't have the additional task of operating the software. No personal data is
asked for (e.g. email addresses), no tracking data is being
collected (e.g. IP addresses) and the entries are anonymised. 

We'll be making the results and the anonymised data available under the
[Creative Commons CCO](https://creativecommons.org/public-domain/cc0/):
that way anyone can analyse the data for further insights.

We hope the results of the survey will be used to understand both the Guix
project's strengths and areas we can improve. Which is why your input is
so important.  If you can, please take the survey!

[Take the survey now!](https://guix.limesurvey.net/216541)



             reply	other threads:[~2024-11-10 12:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-10 12:00 Steve George [this message]
2024-11-10 14:01 ` [bug#74291] [Website patch] Announcing the Guix user survey - blog post pelzflorian (Florian Pelz)
2024-11-11  9:14   ` bug#74291: " Christopher Baines

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=bb0f4c02-5107-4ef6-9268-4748eae0d156@futurile.net \
    --to=steve@futurile.net \
    --cc=74291@debbugs.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).