all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: L p R n d n <guix@lprndn.info>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Communication and Design at Guix
Date: Tue, 15 Jan 2019 11:36:20 +0100	[thread overview]
Message-ID: <CAJ3okZ3OJcHjxYsEkLkofMFcXgvFoOY_TSqcHK9614jr2LYZuA@mail.gmail.com> (raw)
In-Reply-To: <cucmuo31dux.fsf@lprndn.info>

Dear,

If I may, I would say that no manual can satisfy every reader; in
terms of rendering (menu, color, etc.) and in terms of content (deep
details or not, etc.).

About the rendering, some of us like to browse with Emacs and
info-mode, other prefer Web-style. There is no general pattern. :-)

About the content, I agree that the GNU manuals are intimidating for
newcomers because they are exhaustive, and the newcomers---as me---are
lost in all the details.
I also agree that someone often finds something in GNU manuals only if
they knows what they is looking for.
However, the GNU manuals are so useful once you are emancipated enough. :-)

An Introduction to Programming in Emacs Lisp spots well the different
kind of reader:
https://www.gnu.org/software/emacs/manual/html_node/eintr/Who-You-Are.html#Who-You-Are
It appears to me really a good companion to the heavy Elisp manual. I
mean one complements the other; depending on the reader's skills and
on they learns.

As a newcomer, what lacks in the Guix documentation are concrete
examples and use cases. They exist but they are scattered: blog post,
Pjotr's docs, etc.
A section with examples should be nice, e.g., some subsection as: Guix
for the impatient, Guix for the Web dev, Guix for the Scientific, Guix
for Pythonista, Guix for the Conda user, etc.
From my opinion, it is in the same direction than the effort about the
videos (current outreachy); if I am understanding well.


All the best,
simon

  reply	other threads:[~2019-01-15 10:36 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08 16:49 Communication and Design at Guix L p R n d n
2019-01-08 17:37 ` Ludovic Courtès
2019-01-09  6:11   ` swedebugia
2019-01-09 21:45     ` Ludovic Courtès
2019-01-10 12:09       ` L p R n d n
2019-01-10 13:20         ` swedebugia
2019-01-10 14:34         ` Ricardo Wurmus
2019-01-13 21:45           ` Ludovic Courtès
2019-01-14 15:02             ` L p R n d n
2019-01-15 10:36               ` zimoun [this message]
2019-01-15 18:03                 ` nly
2019-01-15 22:08                   ` Ricardo Wurmus
2019-01-16 11:00                     ` Giovanni Biscuolo
2019-01-15 22:28               ` Ludovic Courtès
2019-01-14 23:25             ` swedebugia
2019-01-15 13:56               ` Ricardo Wurmus
2019-01-15 17:39                 ` Julien Lepiller
2019-01-15 22:30                   ` Ludovic Courtès
2019-01-10 12:17     ` L p R n d n
2019-01-10 12:57   ` L p R n d n
2019-01-10 14:30     ` Ricardo Wurmus
2019-01-13 21:50     ` Ludovic Courtès
2019-01-14 14:36       ` L p R n d n
2019-01-15 22:31         ` Ludovic Courtès
2019-01-16 16:31       ` George Clemmer
2019-01-17  0:10         ` swedebugia
2019-01-17 10:58         ` L p R n d n
2019-01-17 11:10           ` Ricardo Wurmus
2019-01-17 14:08             ` swedebugia
2019-01-17 16:24               ` L p R n d n

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=CAJ3okZ3OJcHjxYsEkLkofMFcXgvFoOY_TSqcHK9614jr2LYZuA@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=guix@lprndn.info \
    /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.