unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>,
	Wilko Meyer <w@wmeyer.eu>
Cc: guix-devel@gnu.org
Subject: Re: Guix Survey (follow up on "How can we decrease the cognitive overhead for contributors?")
Date: Thu, 12 Oct 2023 16:43:16 +0200	[thread overview]
Message-ID: <868r873nqz.fsf@gmail.com> (raw)
In-Reply-To: <2ae35de1-0e77-7652-43df-b8ff3622eb00@gmail.com>

Hi,

On Mon, 09 Oct 2023 at 12:29, Katherine Cox-Buday <cox.katherine.e@gmail.com> wrote:

> Is this rough list of questions our first pass at what the survey should 
> contain?
>
> Have you done any more research on what other communities are doing?
>
> What are next steps?

Well, from my opinion, since the idea is to send once a year this
survey, the next steps seems sending a first patch.  Let say the Git
repository maintenance under doc/ and plain text file (or Org or
Markdown).

https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/doc

Then, as any other change, we can comment and iterate (v2, v3, etc.)
until we are fine with the questions and wordings.  Once we have some
LGTM, let install the file.

End of step 1-a.  In parallel, step 1-b: how to distribute the survey
and collect answers?

Then step 2.  Etc. :-)

WDYT?

Cheers,
simon


  reply	other threads:[~2023-10-12 14:44 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 [this message]
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=868r873nqz.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=cox.katherine.e@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).