From: MSavoritias <email@msavoritias.me>
To: Blake Shaw <blake@reproduciblemedia.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: What's to be considered on-topic for Guile mailing lists? (Re: The message chain with an happy ending)
Date: Thu, 06 Jul 2023 13:37:09 +0300 [thread overview]
Message-ID: <874jmh8gv2.fsf@fannys.me> (raw)
In-Reply-To: <2f6ad68d-02b7-4b17-888a-aedd3eb07733@reproduciblemedia.com>
No worries. The remakr was not to point fingers at anybody.
I could do a better job by askid more questions too :P
MSavoritias
Blake Shaw <blake@reproduciblemedia.com> writes:
> 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.
>
> On Jul 6, 2023, at 02:53, MSavoritias <email@msavoritias.me> wrote:
>
> Olivier Dion <olivier.dion@polymtl.ca> writes:
>
> On Wed, 05 Jul 2023, Maxime Devos <maximedevos@telenet.be> wrote:
>
> the Guile department isn't really alive, but that's just because of lack
> of applicants and interest in working on Guile itself, not because of a
> bad work environment.
>
> On that matter, I do think lots of people are interested to work on
> Guile core itself, myself included. However, I find it difficult to
> contribute in general and to have feedback.
>
> As a person learning guile right now for an xmpp client the
> documentation is the biggest barrier. Followed by practical examples and
> how to do stuff with libraries.
>
> For example we have https://lispcookbook.github.io/cl-cookbook/
> for common lisp which is something I had in mind with the second
> sentence.
>
> MSavoritias
next prev parent reply other threads:[~2023-07-06 10:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 7:26 The message chain with an happy ending Stefan Israelsson Tampe
2023-07-02 8:24 ` Maxime Devos
2023-07-02 14:43 ` Stefan Israelsson Tampe
2023-07-05 10:21 ` Maxime Devos
2023-07-05 10:42 ` Blake Shaw via Developers list for Guile, the GNU extensibility library
2023-07-05 11:06 ` What's to be considered on-topic for Guile mailing lists? (Re: The message chain with an happy ending) Maxime Devos
2023-07-05 13:58 ` Olivier Dion
2023-07-05 15:30 ` MSavoritias
2023-07-05 20:05 ` Blake Shaw
2023-07-06 10:37 ` MSavoritias [this message]
2023-07-05 11:08 ` The message chain with an happy ending Maxime Devos
2023-07-05 11:17 ` Thompson, David
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=874jmh8gv2.fsf@fannys.me \
--to=email@msavoritias.me \
--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).