unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mike Gran <spk121@yahoo.com>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: "Blake Shaw" <blake@nonconstructivism.com>,
	"Taylan Kammer" <taylan.kammer@gmail.com>,
	"Ludovic Courtès" <ludo@gnu.org>,
	"Jean Abou Samra" <jean@abou-samra.fr>,
	guile-devel@gnu.org
Subject: Re: Maintenance and future of Guile
Date: Sun, 19 Dec 2021 13:50:20 -0800	[thread overview]
Message-ID: <Yb+pHHZf6v0K94oF@spikycactus.com> (raw)
In-Reply-To: <87pmpscnbq.fsf@laura>

On Sun, Dec 19, 2021 at 04:11:05PM -0500, Olivier Dion via Developers list for Guile, the GNU extensibility library wrote:
> On Mon, 20 Dec 2021, Blake Shaw <blake@nonconstructivism.com> wrote:
> > In a situation like this, I would recommend that we form a little
> > working group to collectively study the implementation of Guile, and
> > with Ludo's suggestions come up with a roadmap for tackling various
> > areas of the repo/compiler/infrastructure that need work, which we
> > could then divide up among ourselves with each of us creating a
> > presentation on our assigned areas, with group hack sessions following
> > each bi-weekly (or whatever) presentation. This way we could
> > distribute the knowledge aquisicition work in a structured fashion
> > while forming a support group for developing a collective
> > understanding of the codebase, as a cohort of sorts.
> 
> I think that would be a great idea.  Separating the work across our
> respective forces would be beneficial to the project.  However, that
> would require someone that can organize this workgroup and give it some
> inertia and a direction on where to start.

For what it is worth, I'm a committer, and I've done a fair amount of
patching of core Guile, sporadically over the years.  So I can at least
help a bit.  I know my way around the C side of things.

But also, historically, my availability varies wildly with family,
health, and day job.

v/r
Mike Gran



  reply	other threads:[~2021-12-19 21:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-19 20:05 Maintenance and future of Guile Blake Shaw
2021-12-19 20:41 ` Maxime Devos
2021-12-19 21:11 ` Olivier Dion via Developers list for Guile, the GNU extensibility library
2021-12-19 21:50   ` Mike Gran [this message]
2021-12-20 14:57 ` Tim Van den Langenbergh
  -- strict thread matches above, loose matches on Subject: below --
2021-12-29 21:05 Blake Shaw
2021-12-29 21:57 ` Olivier Dion via Developers list for Guile, the GNU extensibility library
2021-12-20 18:53 Blake Shaw
2021-12-29 16:23 ` Olivier Dion via Developers list for Guile, the GNU extensibility library
2021-12-29 19:57   ` Dr. Arne Babenhauserheide
2021-12-15 13:35 Blake Shaw
2021-12-15 14:07 ` Ludovic Courtès
2021-12-13 22:18 Maintenance and future of Guile (was: [patch] Add instructions for sending patches) Jean Abou Samra
2021-12-15 10:20 ` Maintenance and future of Guile Ludovic Courtès
2021-12-16 21:15   ` Taylan Kammer
2021-12-17 14:51     ` Olivier Dion via Developers list for Guile, the GNU extensibility library
2021-12-17 15:33       ` Artem Chernyak
2021-12-17 15:37       ` Ludovic Courtès
2021-12-17 15:48         ` Olivier Dion via Developers list for Guile, the GNU extensibility library
2021-12-18 16:35           ` Taylan Kammer
2021-12-21 14:27           ` Ludovic Courtès
2022-08-19 16:49             ` Aleix Conchillo Flaqué
2022-08-19 18:46           ` zimoun
2022-08-19 19:06             ` 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=Yb+pHHZf6v0K94oF@spikycactus.com \
    --to=spk121@yahoo.com \
    --cc=blake@nonconstructivism.com \
    --cc=guile-devel@gnu.org \
    --cc=jean@abou-samra.fr \
    --cc=ludo@gnu.org \
    --cc=olivier.dion@polymtl.ca \
    --cc=taylan.kammer@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.
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).