unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neiljerram@gmail.com>
To: Blake Shaw <blake@nonconstructivism.com>
Cc: guix-user@gnu.org, guile-user <guile-user@gnu.org>, guix-days@gnu.org
Subject: Re: Proposal: Deep Dive into the Guile Docs & Makeover Proposal
Date: Tue, 8 Feb 2022 09:07:53 +0000	[thread overview]
Message-ID: <CAKuG=vtHz7KCdwB6cH_=n2arKxaNA2YfWRs_uATmch7USz4BLw@mail.gmail.com> (raw)
In-Reply-To: <87tud9olma.fsf@nonconstructivism.com>

Hi Blake,

On Tue, 8 Feb 2022 at 08:55, Blake Shaw <blake@nonconstructivism.com> wrote:
> [...]
>
> Serving at once as a referrence manual & API specification, the large size may in part be attributed to what simultaneously makes Guile an appealing project to contribute to, while also rendering the documentation process somewhat delicate: Guile is a massive collective project featuring the contributions of many authors over the course of three decades, contributions which Guilers would hate to trivialize or treat as insignificant or edit away on a whim. Additionally, Guile comes from a long set of traditions within Scheme hacking which itself is deep with sage wisdom spanning many pedagogical philosophies and one of the greatest literature traditions of hacker culture. Is it possible to perform a makeover of the Guile Documentation while respecting these historical threads, at once rendering it more approachable for new users while not forsaking the deep nuggets of wisdom that lie therein?
>
> Since mid-December I have been mulling over these questions as newcomer, both studying & analyzing the docs, and trying to come to grips with it's strengths and shortcomings. For this talk, I will present my research to the Guix community, culminating with a plan for a full makeover of the existing docs which would respect the above concerns. I will use the 5 minute presentation to focus on the plan of action, with hopes that during the Q&A we can come to consensus on what is to be done. The decisions made by the group will form the basis of a proposal to be made to the Guile community, and once everyone is in agreement with plans for how to move forward I will undertake the effort to implement the makeover proposal.

Speaking as one of the past authors of the manual, I look forward to
hearing your thoughts.  It is genuinely challenging to present this
amount of material and explain its complexity, and there is no reason
at all to consider any current arrangement as cast in stone.  Thanks
for thinking about this.

Best wishes,
    Neil



  reply	other threads:[~2022-02-08  9:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08  7:36 Proposal: Deep Dive into the Guile Docs & Makeover Proposal Blake Shaw
2022-02-08  9:07 ` Neil Jerram [this message]
2022-02-08 11:46   ` Blake Shaw
2022-02-08 15:22     ` Daniel Tornabene
2022-02-08 10:16 ` Jérémy Korwin-Zmijowski
2022-02-08 14:45 ` james
2022-02-08 15:08 ` Olivier Dion via General Guile related discussions
2022-02-08 17:25   ` Daniel Tornabene
2022-02-10 17:20 ` Christine Lemmer-Webber
  -- strict thread matches above, loose matches on Subject: below --
2022-02-08 13:06 Blake Shaw
2022-02-08 15:21 Blake Shaw
2022-02-08 16:59 Blake Shaw
2022-02-08 17:28 ` Daniel Tornabene
2022-02-16 22:06 Blake Shaw
2022-02-17 16:58 Blake Shaw
2022-02-18 17:48 ` Olivier Dion via General Guile related discussions
2022-02-19 12:17 ` Neil Jerram
2022-02-19 15:33   ` Olivier Dion via General Guile related discussions
2022-02-19 17:35     ` adriano
2022-02-18 18:05 Blake Shaw

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='CAKuG=vtHz7KCdwB6cH_=n2arKxaNA2YfWRs_uATmch7USz4BLw@mail.gmail.com' \
    --to=neiljerram@gmail.com \
    --cc=blake@nonconstructivism.com \
    --cc=guile-user@gnu.org \
    --cc=guix-days@gnu.org \
    --cc=guix-user@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).