From: Benson Muite <benson_muite@emailplus.org>
To: gfortran <fortran@gcc.gnu.org>
Subject: Re: Team Collaboration Considerations
Date: Thu, 19 Jan 2023 08:00:54 +0300 [thread overview]
Message-ID: <397bf74b-4528-f4a8-5a7e-88e7ba10bb38@emailplus.org> (raw)
In-Reply-To: <CAF1jjLtmLNuSJ8qcm8PgWjRecX=jHoGQM5wLZDQx4cXeMVQjXg@mail.gmail.com>
On 12/26/22 13:19, NightStrike via Fortran wrote:
> On Tue, Dec 13, 2022, 03:10 Janne Blomqvist via Fortran <fortran@gcc.gnu.org>
> wrote:
>
>> But in general, yes, I do think IRC is showing its age in an
>> increasingly multi-device and mobile world.
>>
>
> Tools like irccloud help here. I guess that doesn't qualify as open source
> though.
>
>>
Might a GSOC project examining community health be something that could
produce useful recommendations on improving developer efficiency and
getting new contributors? The project can also produce a monitoring
system that fits the GCC workflow. A chat tool is helpful (Rust uses
Zulip https://gcc-rust.zulipchat.com), but it seems understanding how
the project develops and keeping track of relevant information are
greater obstacles.
The GCC workflows is quite different from other open source projects
being primarily email based and not using a bug tracker. Email does
work well, and has been adapted in Sourcehut, but they have had to
introduce a tutorial:
https://git-send-email.io/
next prev parent reply other threads:[~2023-01-19 5:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 3:52 Jerry D
2022-12-04 14:16 ` Benson Muite
2022-12-08 1:54 ` Jerry D
2022-12-08 4:12 ` Benson Muite
2022-12-08 16:27 ` Steve Kargl
2022-12-08 17:25 ` Tobias Burnus
2022-12-10 18:15 ` Jerry D
2022-12-08 19:14 ` Holcomb, Katherine A (kah3f)
2022-12-09 19:36 ` Toon Moene
2022-12-09 21:56 ` Paul Richard Thomas
2022-12-09 22:10 ` Toon Moene
2022-12-10 20:10 ` Jerry D
2022-12-10 21:09 ` Steve Kargl
2022-12-11 17:37 ` Holcomb, Katherine A (kah3f)
2022-12-10 21:11 ` Thomas Koenig
2022-12-13 8:10 ` Janne Blomqvist
2022-12-13 12:22 ` Jerry D
2022-12-26 10:19 ` NightStrike
2023-01-19 5:00 ` Benson Muite [this message]
2023-01-19 12:28 ` NightStrike
2023-01-19 12:46 ` Toon Moene
2023-01-19 12:52 ` NightStrike
2023-01-19 18:33 ` Bernhard Reutner-Fischer
2023-01-19 19:03 ` NightStrike
2023-01-20 6:11 ` Bernhard Reutner-Fischer
2023-01-20 6:21 ` Benson Muite
2023-01-21 4:50 ` Jerry D
2022-12-08 21:27 Harald Anlauf
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=397bf74b-4528-f4a8-5a7e-88e7ba10bb38@emailplus.org \
--to=benson_muite@emailplus.org \
--cc=fortran@gcc.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).