all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Wilko Meyer <w@wmeyer.eu>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Guix Survey (follow up on "How can we decrease the cognitive overhead for contributors?")
Date: Mon, 06 Nov 2023 23:46:15 +0100	[thread overview]
Message-ID: <874jhybi1p.fsf@wmeyer.eu> (raw)
In-Reply-To: <2ae35de1-0e77-7652-43df-b8ff3622eb00@gmail.com>


Hi Katherine,

I haven't had too much time lately in regards of the survey, but hope
I'll be able to commit more time to it throughout the next weeks. Thanks
for reviewing the first rough draft of the questions!

Katherine Cox-Buday <cox.katherine.e@gmail.com> writes:

> Does the GNU project have a "general translation" team?
>
> Maybe some of our Guix community members who speak multiple languages
> would be willing to translate the survey into their primary language?

I'm not too familiar with the structures of the GNU project; but there's
a page mentioning translation teams for several languages at
least[0]. Don't know how active these teams are, so maybe reaching out
to other community members on this list would be a better bet?

> My opinion is that we should not do free form questions for this first
> time. We're new at this, we have enough topics to cover, and the
> topics we are covering seem to cause a lot of discussion (that's good)
> which could lead to a lot of text to read through.

Agreed, having quantitative questions only already seems like a good
amount of work; even though free form would be quite interesting,
that's, as you said, out of scope for the first survey.

> Have you done any more research on what other communities are doing?

I did! Hope I'll be able to write a good cohesive summary of my org-roam
notes on this to share in this thread soon-ish.

> What are next steps?

I think Simons idea of collecting our questions somewhere and improving
those until we're happy/able to start the survey period sounds like a
good plan. If time permits, I'll put the rough list of questions we have
now in a .org document and open an issue containing them; so we have a
place where the survey questions can be edited/improved/discussed. WDYT?

[0]: https://www.gnu.org/server/standards/README.translations.en.html#teams

-- 
Kind regards,

Wilko Meyer
w@wmeyer.eu


  parent reply	other threads:[~2023-11-06 23:04 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=874jhybi1p.fsf@wmeyer.eu \
    --to=w@wmeyer.eu \
    --cc=cox.katherine.e@gmail.com \
    --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 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.