unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Matt <matt@excalamus.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix wiki
Date: Tue, 18 Jan 2022 15:34:37 +0100	[thread overview]
Message-ID: <87ee55glj6.fsf@gnu.org> (raw)
In-Reply-To: <17e4c5403ca.e72c7b19372548.5993925318643575057@excalamus.com> (matt@excalamus.com's message of "Tue, 11 Jan 2022 22:28:01 -0500")

Hi,

Matt <matt@excalamus.com> skribis:

>  ---- On Tue, 11 Jan 2022 18:18:25 -0500 Ricardo Wurmus <rekado@elephly.net> wrote ----
>
>  > This is where we disagree.  I’ve wasted so much time in my life
>  > following outdated or wrong instructions on forums or wikis.  I really
>  > don’t want to see anything half-baked anywhere near this project.  There
>  > are few things that frustrate me more than well-meaning but misleading
>  > advice.
>  
> Do you know that the libreplanet wiki is linked to from the main Guix page?  https://guix.gnu.org/ > Help > Wiki

We are aware of this wiki; it has its uses, such as synchronizing for
FOSDEM, GSoC, and other events, but we never intended to use it for
documentation.

It’s unfortunate that your reply to Ricardo dismisses their advice.  It
really boils down to this: read bits of the manual and cookbook that
matter to your use cases, articulate what you think is missing or poorly
structured, and propose changes or new text.

It’s much easier to make progress looking at concrete, focused changes
than in the abstract.

Thanks in advance,
Ludo’.


  reply	other threads:[~2022-01-18 15:46 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
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 [this message]
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=87ee55glj6.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=matt@excalamus.com \
    /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).