From: Olivier Dion via "Developers list for Guile, the GNU extensibility library" <guile-devel@gnu.org>
To: Blake Shaw <blake@nonconstructivism.com>,
"Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: Tim Van den Langenbergh <tmt_vdl@gmx.com>, guile-devel@gnu.org
Subject: Re: Maintenance and future of Guile
Date: Wed, 29 Dec 2021 16:57:31 -0500 [thread overview]
Message-ID: <87pmpfjcqc.fsf@laura> (raw)
In-Reply-To: <87h7arjf5o.fsf@nonconstructivism.com>
On Thu, 30 Dec 2021, Blake Shaw <blake@nonconstructivism.com> wrote:
> If we're all dedicated emacsians, it could be as simple as setting up
> cron jobs to pull at regular intervals, and could shed some insight onto
> "guix native" development and its challenges.
If it's okay with everyone, I think that would be awesome. Given what
Dr. Arne said, I think we can use it for management of the team.
The next things to do (none exhaustive) I guess would be:
1. Make a list of contributors that want to participate
2. Make a a list of what's to be done and in which priority
3. Setup the management workflow with org-mode and distribute the work
among contributors
P.S: I'm not sure why, but when you reply (Blake), there's another
mail chain spawning in my MUA instead of following the previous chain. It's
nothing concerning, but it does break the flow of mail conversation.
--
Olivier Dion
Polymtl
next prev parent reply other threads:[~2021-12-29 21:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 21:05 Maintenance and future of Guile Blake Shaw
2021-12-29 21:57 ` Olivier Dion via Developers list for Guile, the GNU extensibility library [this message]
-- strict thread matches above, loose matches on Subject: below --
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-19 20:05 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
2021-12-20 14:57 ` Tim Van den Langenbergh
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=87pmpfjcqc.fsf@laura \
--to=guile-devel@gnu.org \
--cc=arne_bab@web.de \
--cc=blake@nonconstructivism.com \
--cc=olivier.dion@polymtl.ca \
--cc=tmt_vdl@gmx.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).