From: "Thompson, David" <dthompson2@worcester.edu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>, Craig Barnes <cjbarnes18@gmail.com>
Subject: Re: Should we start a Guix users wiki?
Date: Tue, 8 Sep 2015 08:40:58 -0400 [thread overview]
Message-ID: <CAJ=RwfZ_et-S7njzwFVfX1ARj1gBrTc3=hW-2nvq05_H96G=GQ@mail.gmail.com> (raw)
In-Reply-To: <87pp1tnsna.fsf@gnu.org>
On Tue, Sep 8, 2015 at 5:54 AM, Ludovic Courtès <ludo@gnu.org> wrote:
> 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.
+1
- Dave
next prev parent reply other threads:[~2015-09-08 12:41 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
2015-09-08 12:40 ` Thompson, David [this message]
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='CAJ=RwfZ_et-S7njzwFVfX1ARj1gBrTc3=hW-2nvq05_H96G=GQ@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=cjbarnes18@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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.