From: Matt <matt@excalamus.com>
To: "blake" <blake@reproduciblemedia.com>
Cc: "guile-devel" <guile-devel@gnu.org>
Subject: Guile documentation overhaul (was Re: What's to be considered on-topic for Guile mailing lists?)
Date: Wed, 18 Oct 2023 21:13:11 +0200 [thread overview]
Message-ID: <18b4434c6b6.d33f2003967855.7638861381500962971@excalamus.com> (raw)
---- On Thu, 06 Jul 2023 13:37:09 +0300 Blake wrote ---
> I'm sorry, I'm the one supposed to be working on a rehaul of the documentation, but the review process has slowed this down. I started integrating
> everyones suggestions for the revamped map section after it was proposed in January and its almost done but not complete, and but I've been so
> busy the past few months its really my last priority and given the extent of the changes demanded its a lot of work.
Hi! I just got the paperwork worked out between the FSF and my employer. I have a strong interest in helping to improve the Guile documentation. I tried searching the archives for information about a "rehaul" and found nothing. Can someone tell me more? Are there any threads discussing it?
reply other threads:[~2023-10-18 19:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18b4434c6b6.d33f2003967855.7638861381500962971@excalamus.com \
--to=matt@excalamus.com \
--cc=blake@reproduciblemedia.com \
--cc=guile-devel@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).