From: Oliver Propst <oliver.propst@fripost.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>, calcium <calcium@disroot.org>
Subject: Re: Planet of Guix-related posts?
Date: Wed, 12 Jan 2022 10:23:52 +0100 [thread overview]
Message-ID: <268d0f17a7472f22311988d23d77bef6@fripost.org> (raw)
In-Reply-To: <87mtk15p2o.fsf@elephly.net>
As someone how cares deeply about Guix I can state I think that the
Cookbook is a great resource.
I feels like the Cookbook have a clear focus on quality documentation
and has to life only as a result of lots hard work and love for the Guix
project. That said even as a technical person I do must admit that find
some segment and concepts in the cookbook as hard to read and understand
(especially from the the perspective of a non-technical person). So
guess a relevant question could be how do we make the Guix documentation
easier to understand for everybody and how do we improve the
explanations of the current segments in the Cookbook.
--
Kinds regards Oliver Propst
https://twitter.com/Opropst
next prev parent reply other threads:[~2022-01-12 9:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.34870.1641617883.18145.guix-devel@gnu.org>
2022-01-08 8:42 ` Guix Documentation Meetup calcium
2022-01-08 11:35 ` Ricardo Wurmus
2022-01-08 11:49 ` calcium
2022-01-08 16:24 ` Matt
2022-01-08 18:58 ` Ricardo Wurmus
2022-01-08 19:06 ` Leo Famulari
2022-01-09 21:12 ` Matt
2022-01-10 9:05 ` André A. Gomes
2022-01-10 13:40 ` Matt
2022-01-10 16:05 ` André A. Gomes
2022-01-11 18:45 ` Matt
2022-01-12 18:41 ` Leo Famulari
2022-01-13 0:04 ` Matt
2022-01-10 15:21 ` Planet of Guix-related posts? zimoun
2022-01-11 13:38 ` Matt
2022-01-12 1:40 ` Matt
2022-01-12 5:17 ` André A. Gomes
2022-01-12 8:30 ` Ricardo Wurmus
2022-01-12 9:23 ` Oliver Propst [this message]
2022-01-12 8:36 ` Ricardo Wurmus
2022-01-13 0:22 ` Guix Documentation Meetup Leo Famulari
2022-01-13 13:15 ` ilmu
2022-01-08 13:41 ` Matt
2022-01-08 14:09 ` Julien Lepiller
2022-01-08 14:54 ` Matt
2022-01-08 14:39 ` Josselin Poiret
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=268d0f17a7472f22311988d23d77bef6@fripost.org \
--to=oliver.propst@fripost.org \
--cc=calcium@disroot.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).