unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: yoosty@gmail.com
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Quick-start guide
Date: Sat, 11 Jun 2016 13:49:55 -0400	[thread overview]
Message-ID: <20160611174955.GA9544@jasmine> (raw)
In-Reply-To: <CAGSLf808YCZh6n48yMdgMfVugBqWV3OgGpmK1PK-Tme5H_UJRQ@mail.gmail.com>

On Sat, Jun 11, 2016 at 06:43:21AM -0700, yoosty@gmail.com wrote:
> Upon further reflection.. The Guix manual might not be an appropriate place
> for such a guide. If the Guix manual isn't a good place for such a set of
> instructions, do you have any suggestions for a location (blog, etc)?

There is this useful wiki managed by Raymond Nicholson:
https://gitlab.com/rain1/guix-wiki/wikis/home

Although, I'd like to echo Ludovic's question, and also say that the
goal of the manual is to be completely sufficient for first-timers and
experienced users alike.

I find the phenomenon of 3rd party wikis giving instructions on how to
use some piece of software to be a dismaying "antipattern". And, the
situation only gets worse as people send documentation to the 3rd party
wiki instead of to the software project in questoin.

So, please tell us of any specific shortcomings! It seems that you would
prefer "System Installation" to begin with an outline?

  reply	other threads:[~2016-06-11 17:50 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 [this message]
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
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=20160611174955.GA9544@jasmine \
    --to=leo@famulari.name \
    --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).