From: Neil Jerram <firstname.lastname@example.org>
To: Catonano <email@example.com>
Cc: guile-devel <firstname.lastname@example.org>,
Vijay Marupudi <email@example.com>
Subject: Re: a cookbook
Date: Wed, 16 Feb 2022 09:54:09 +0000 [thread overview]
Message-ID: <CAKuG=vttqqUeBG6aH_hk5mJC5psgfFe0HcfGTCB-2MR=2DDYHA@mail.gmail.com> (raw)
On Wed, 16 Feb 2022 at 09:04, Catonano <firstname.lastname@example.org> wrote:
> Il giorno lun 14 feb 2022 alle ore 18:01 Vijay Marupudi <email@example.com> ha scritto:
>> > Is there any interest/possibility to have such a cookbook hosted
>> > within the Guile official documentation (as it is for Guix) ?
>> I personally think that a Cookbook should be an independent effort, with
>> links from the Guile Manual if possible. This would lighten the load on
>> the maintainers, and allow for quicker collaboration.
> but then the discoverability of the cookbook would be diminished 🙁
Yes, agree that the resulting cookbook needs to be easily
discoverable. Perhaps that means that if you install a guile-doc
package, it appears as a top-level Info item like Guile Reference
does. Perhaps it doesn't need to be quite as specific as that.
(Although personally I really like doc being available locally, e.g.
in Info form, instead of always going online.)
But as you also say...
> As for you creating a web site, I'd prefer such a website to be a communitarian effort, rather than depend on a single person
> Maybe a wiki on Gitlab could do and it could have several mantainers ?
> I'd be happy to be one
Yes, definitely feels right to crowd-source this, instead of having it
centralized in the core Guile repo.
It feels to me that with the right structure in place, people will
readily come and contribute the detailed material to it. So it's
worth spending a little time to decide the right structure.
next prev parent reply other threads:[~2022-02-16 9:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 6:44 a cookbook Catonano
2022-02-14 15:47 ` Max Brieiev
2022-02-14 16:56 ` Olivier Dion via Developers list for Guile, the GNU extensibility library
2022-02-16 7:12 ` Catonano
2022-02-14 17:01 ` Vijay Marupudi
2022-02-16 7:21 ` Catonano
2022-02-16 9:54 ` Neil Jerram [this message]
2022-02-16 21:13 ` Catonano
2022-02-19 13:18 ` Neil Jerram
2022-02-20 11:07 ` Catonano
2022-02-16 14:19 ` Olivier Dion via Developers list for Guile, the GNU extensibility library
2022-02-17 2:11 ` Vijay Marupudi
2022-02-17 7:00 ` Catonano
2022-02-17 17:34 ` Vijay Marupudi
2022-02-14 22:00 dsmich
2022-02-14 23:06 ` Vijay Marupudi
2022-02-18 14:32 dsmich
2022-02-20 0:48 ` Vijay Marupudi
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:
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 \
* 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).