unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Matt <matt@excalamus.com>
To: "Ricardo Wurmus" <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix wiki
Date: Tue, 11 Jan 2022 21:52:46 -0500	[thread overview]
Message-ID: <17e4c33bd4a.c10c13ea370372.1632975886725925499@excalamus.com> (raw)
In-Reply-To: <87h7aa7108.fsf@elephly.net>

 ---- On Tue, 11 Jan 2022 10:17:43 -0500 Ricardo Wurmus <rekado@elephly.net> wrote ----
 > 
 > Matt <matt@excalamus.com> writes:
 > 
 > > To me, it says something like, we don't actually care about your
 > > contribution: you have to literally buy in first.
 > 
 > No, you do not.
 
I stand corrected.  Luis Felipe kindly pointed out what I had overlooked.

https://lists.gnu.org/archive/html/guix-devel/2022-01/msg00194.html

 > I see a lot of emotional language here, but the fact is: you can
 > contribute to our documentation by sending your text.  It’s that
 > simple. 

I'm sorry if you felt accused. I can see how it might come across that way.  It would have been better for me to just ask if I was missing something (which I was).

 > Send an email to guix-devel or guix-patches with a suitable subject so
 > that it doesn’t get lost in a discussion and take it from there.
 > 
 > > I feel like it also
 > > says that community isn't important to us.
 > 
 > I do not share your interpretation of the situation.

I'm glad because that means we're in agreement now that I see my mistake. :)


  reply	other threads:[~2022-01-12  2:53 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09 21:14 Guix wiki Matt
2022-01-09 21:32 ` Vagrant Cascadian
2022-01-11 13:02   ` Matt
2022-01-11 18:29   ` Jonathan McHugh
2022-04-13 14:46   ` Aurora
2022-01-09 23:55 ` Vincent Legoll
2022-01-11 13:31   ` Matt
2022-01-11 15:17     ` Ricardo Wurmus
2022-01-12  2:52       ` Matt [this message]
2022-01-11 15:30     ` Tobias Geerinckx-Rice
2022-01-11 17:15       ` zimoun
2022-01-11 17:27         ` Tobias Geerinckx-Rice
2022-01-11 18:21           ` André A. Gomes
2022-01-11 18:50           ` zimoun
2022-01-12  2:06             ` Tobias Geerinckx-Rice
2022-01-12  8:55               ` zimoun
2022-01-12  9:22                 ` André A. Gomes
2022-01-12  3:51       ` Matt
2022-01-12 15:26         ` Luis Felipe
2022-01-11 16:48     ` Luis Felipe
2022-01-11 21:03     ` Attila Lendvai
2022-01-11 23:18       ` Ricardo Wurmus
2022-01-12  3:28         ` Matt
2022-01-18 14:34           ` Ludovic Courtès
2022-04-11  6:49             ` Attila Lendvai
2022-04-11  8:42               ` Maxime Devos
2022-04-13 15:01                 ` Attila Lendvai
2022-04-11  8:47               ` Maxime Devos
2022-01-12 11:19         ` Attila Lendvai
2022-01-12 11:52           ` Ricardo Wurmus
2022-01-12 12:00           ` André A. Gomes
2022-01-10  8:29 ` Josua Stingelin
2022-01-12  1:57   ` Matt
2022-01-12  9:19     ` Ricardo Wurmus
2024-01-10  9:55 ` Attila Lendvai
2024-01-17 19:17   ` Maxim Cournoyer

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=17e4c33bd4a.c10c13ea370372.1632975886725925499@excalamus.com \
    --to=matt@excalamus.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).