From: Ricardo Wurmus <rekado@elephly.net>
To: help-guix@gnu.org
Cc: rendaw <7e9wc56emjakcm@s.rendaw.me>
Subject: Guix cookbook (was: guile scheme tutorial)
Date: Wed, 08 May 2019 22:21:15 +0200 [thread overview]
Message-ID: <871s18elz8.fsf@elephly.net> (raw)
In-Reply-To: <871s19w0ik.fsf@ambrevar.xyz>
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> A well written manual might not be the only answer we are looking for. How
> do we teach complex concepts in schools? With examples and exercises.
> Maybe we should do that. Blog articles could be a good fit.
I’m not a fan of blog posts for teaching, because they quickly lose
relevance. An example: recently someone on IRC said they were following
your packaging tutorial and something wasn’t working; someone else then
said that the blog post was outdated. I don’t recall the details, but I
find this worrying, because people might spend time learning something
from blog posts only to have to unlearn things again.
Blog posts are great for outreach and to spawn contemporary discussions.
But I think that ultimately we should enhance the manual. We are not
limited to having just one document that needs to meet all
requirements. We can have more than one thing.
Previously, we floated the idea of having a Guix cookbook with short
tutorials showing how to achieve well-defined tasks such as writing a
package (i.e. an updated and distilled version of your blog post
perhaps), setting up a bluetooth-enabled MPD-powered media workstation,
configuring a complex web application with database, web server, etc.
I’d really like to see such a cookbook become part of Guix. It would
always be up-to-date and it can provide much needed examples that might
otherwise clutter up the manual.
What do you think? Shall we start with converting your packaging
tutorial?
--
Ricardo
next prev parent reply other threads:[~2019-05-08 20:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 12:45 guile scheme tutorial amirouche
2019-05-03 17:15 ` Guy fleury
2019-05-03 21:11 ` Laura Lazzati
2019-05-03 23:44 ` amirouche
2019-05-04 1:51 ` rendaw
2019-05-04 6:08 ` rendaw
2019-05-04 8:57 ` Ludovic Courtès
2019-05-07 4:35 ` rendaw
2019-05-08 12:46 ` Ludovic Courtès
2019-05-08 13:15 ` Pierre Neidhardt
2019-05-08 16:35 ` swedebugia
2019-05-13 7:10 ` rendaw
2019-05-13 8:00 ` Pierre Neidhardt
2019-05-08 20:21 ` Ricardo Wurmus [this message]
2019-05-09 15:14 ` Guix cookbook (was: guile scheme tutorial) Pierre Neidhardt
2019-05-09 21:38 ` Ricardo Wurmus
2019-05-13 9:08 ` Guix cookbook swedebugia
2019-05-04 11:02 ` guile scheme tutorial amirouche
2019-05-04 11:25 ` Laura Lazzati
2019-05-07 2:15 ` rendaw
2019-05-07 7:09 ` amirouche
2019-06-06 15:45 ` Laura Lazzati
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=871s18elz8.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=7e9wc56emjakcm@s.rendaw.me \
--cc=help-guix@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.
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).