From: ludo@gnu.org (Ludovic Courtès)
To: yoosty@gmail.com
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Quick-start guide
Date: Thu, 16 Jun 2016 12:51:51 +0200 [thread overview]
Message-ID: <87d1nhieyg.fsf@gnu.org> (raw)
In-Reply-To: <CAGSLf81RN_hs10N_RHHMeMHHQcVT5gYdF9zYqQq_dehwEGi4YQ@mail.gmail.com> (yoosty@gmail.com's message of "Tue, 14 Jun 2016 22:07:58 -0700")
Hi,
yoosty@gmail.com skribis:
> After reading the feedback here and spending some more time in IRC (which
> really drives home the feedback about translations and colloquialisms,
> thanks John) I would like to do the following:
> - Add a contiguous set of examples to the existing "System Installation"
> section (such that if you follow the examples you will almost certainly end
> up with a working system, even if you don't read much of anything else)
You mean OS config examples? Currently there are 3 example
configurations. We could add more, but I wonder if that wouldn’t be too
much for the manual itself (we could still add more to the installation
image, though.)
> - Add at least one more sub-section to "System Installation" that
> introduces users to extending/customizing the initial system's .scm file
> -- Something like a "Where to go from here? Customizing your installation."
> -- A chance to tease users in to Scheme programming
Makes sense. The “Using the Configuration System” section was intended
to achieve this, but maybe it’s failing. Do you think it could be
improved, or is a new section needed, and if so, how should we
articulate both?
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-06-16 10:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 20:00 [PATCH] Quick-start guide yoosty
2016-06-08 12:47 ` Ludovic Courtès
2016-06-11 13:43 ` yoosty
2016-06-11 17:49 ` Leo Famulari
2016-06-12 15:14 ` myglc2
2016-06-12 20:46 ` Ludovic Courtès
2016-06-15 5:07 ` yoosty
2016-06-16 10:51 ` Ludovic Courtès [this message]
2016-06-24 4:55 ` yoosty
2016-06-24 12:36 ` Ludovic Courtès
2016-06-13 0:40 ` John Darrington
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=87d1nhieyg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=yoosty@gmail.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).