unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Blake Shaw <blake@nonconstructivism.com>
To: guix-devel@gnu.org
Cc: zimoun <zimon.toutoune@gmail.com>,
	Pjotr Prins <pjotr.public12@thebird.nl>,
	Oliver Propst <oliver.propst@fripost.org>,
	Manolis Ragkousis <ragkousism@protonmail.com>
Subject: Re: Organising Guix Days
Date: Thu, 30 Dec 2021 09:53:53 +0700	[thread overview]
Message-ID: <87mtkiiz0e.fsf@nonconstructivism.com> (raw)


Hi folks,

Regarding the presentation I'm putting together on the Guile
Documentation, while I have enough material right now to send out a
basic presentation that covers what I believe to be the dominant,
glaring issues of the composition and organization of the docs as well
as how I would go about restructuring them if everyone agrees with the
proposed edits, I'm also starting to uncover some more nuanced
issues with some of the pedagogical folly that appears throughout the
text, and so a few more weeks would probably result in a more
comprehensive study.

So I was thinking, in that case, should I just make the presentation for
Guix Days? That way it could also be presented at a time when other,
perhaps related projects and issues are coming to the fore.

-- 
“In girum imus nocte et consumimur igni”


             reply	other threads:[~2021-12-30  2:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-30  2:53 Blake Shaw [this message]
2021-12-31  6:40 ` Organising Guix Days adriano
  -- strict thread matches above, loose matches on Subject: below --
2021-12-11  1:37 Julien Lepiller
2021-12-11 11:09 ` Gábor Boskovits
2021-12-13  9:07 ` zimoun
2021-12-18 17:56   ` Pjotr Prins
2021-12-20 17:51 ` Ludovic Courtès
2021-12-20 22:37   ` zimoun
2022-01-06 19:54 ` zimoun

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=87mtkiiz0e.fsf@nonconstructivism.com \
    --to=blake@nonconstructivism.com \
    --cc=guix-devel@gnu.org \
    --cc=oliver.propst@fripost.org \
    --cc=pjotr.public12@thebird.nl \
    --cc=ragkousism@protonmail.com \
    --cc=zimon.toutoune@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).