From: ludo@gnu.org (Ludovic Courtès)
To: Craig Barnes <cjbarnes18@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Should we start a Guix users wiki?
Date: Tue, 08 Sep 2015 11:54:01 +0200 [thread overview]
Message-ID: <87pp1tnsna.fsf@gnu.org> (raw)
In-Reply-To: <55EE0ADD.9050701@gmail.com> (Craig Barnes's message of "Mon, 07 Sep 2015 23:08:29 +0100")
Hi,
Craig Barnes <cjbarnes18@gmail.com> skribis:
> Some time ago I asked on IRC about a guix users wiki. Someone suggest
> that I propose one here (sorry it's taken so long).
>
> I think that a wiki would be a good complement to the manual, which
> while quite complete, lacks exhaustive examples (which would be
> impractical).
I have mixed feelings. There are several issues with a Wiki: one can
hardly know which version of the software it’s talking about (whereas
the installed Info pages of PDFs necessarily match the installed
version), and more importantly, it tends to be disorganized,
unmaintained, and often misleading.
I would strongly encourage people to help fix the manual as a first
step. If information that a user deems useful is missing from the
manual, then it’s a bug. I’m willing to make it as simple as possible
to fix the manual. But really, the manual should have all the examples
necessary for people to understand how to tweak things.
There might be cases where specific information doesn’t quite fit in the
manual, like, say, instructions for a specific laptop model. These
could go in a wiki.
Overall, I think it’s fine to have stuff at
<https://libreplanet.org/wiki/Group:Guix/> for instance, but the manual
should clearly remain the primary source of documentation, without any
ambiguity.
So, what would you like to add to the manual? :-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-09-08 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 22:08 Should we start a Guix users wiki? Craig Barnes
2015-09-08 8:01 ` Amirouche Boubekki
2015-09-08 9:54 ` Ludovic Courtès [this message]
2015-09-08 12:40 ` Thompson, David
2015-09-08 14:37 ` Mark H Weaver
2015-09-10 10:47 ` Craig Barnes
2015-09-10 13:58 ` Ludovic Courtès
2015-09-10 15:35 ` Cook, Malcolm
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=87pp1tnsna.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cjbarnes18@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.