From: Olivier Dion via "Developers list for Guile, the GNU extensibility library" <guile-devel@gnu.org>
To: Blake Shaw <blake@nonconstructivism.com>,
Tim Van den Langenbergh <tmt_vdl@gmx.com>
Cc: guile-devel@gnu.org
Subject: Re: Maintenance and future of Guile
Date: Wed, 29 Dec 2021 11:23:22 -0500 [thread overview]
Message-ID: <87wnjnjs79.fsf@laura> (raw)
In-Reply-To: <87mtkvumyk.fsf@nonconstructivism.com>
On Tue, 21 Dec 2021, Blake Shaw <blake@nonconstructivism.com> wrote:
> Tim Van den Langenbergh <tmt_vdl@gmx.com> writes:
>> That sounds like a good idea, though I wonder what the best way to organise it would be.
>>
>> IRC, Mattermost, and Rocket Chat seem like the most obvious options
>> for chat. I don't know what would be best for task management, maybe
>> some out-of-the-box kanban?
>>
>> Ideas, anyone?
>>
>> Vale,
>>
>> -Tim.
>>
>
> irc is good for me, and of course e-mail :)
>
> but for out-of-the-box task management tools, are we all emacs and/or org-mode users
> here? we could agree on a set of features for an org document that ensures
> we all sync consistentally across configurations, and then manage everything on a
> branch of the guile repo. this way as we're researching the codebase, we
> can post links directly to file line numbers, allowing easy
> navigation.
I'm fullstack emacs, but I'm not sure if org-mode would be the best
management tool. I'm using it for my personnal task, but I don't know
if it applies well to a team.
--
Olivier Dion
Polymtl
next prev parent reply other threads:[~2021-12-29 16:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 18:53 Maintenance and future of Guile Blake Shaw
2021-12-29 16:23 ` Olivier Dion via Developers list for Guile, the GNU extensibility library [this message]
2021-12-29 19:57 ` Dr. Arne Babenhauserheide
-- 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-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=87wnjnjs79.fsf@laura \
--to=guile-devel@gnu.org \
--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).