public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Harald Anlauf <anlauf@gmx.de>
To: fortran@gcc.gnu.org
Subject: Team Collaboration Considerations
Date: Thu, 8 Dec 2022 22:27:06 +0100	[thread overview]
Message-ID: <tmtkra$l49$1@ciao.gmane.io> (raw)

Hi Jerry, all,

as already said, the basic issue appears to be the low number
of contributors, most (all?) of which are working on gfortran
in their spare time (like me).  I think it is not likely that
they will commit to being available regularly.

I have used IRC once for a discussion that was really helpful
for me, but we agreed in advance to meet there, and this was
how it worked.  Other tools may work similar or even better.
(The ML was just not appropriate for the type of discussion.)

A collaboration tool could be helpful for introducing newcomers,
for giving advice in trying to understand how the code works,
and maybe when it doesn't.  Caveat: in many respects I still
feel as close to being a newcomer.

Though I could give a very basic introduction to working with
git, also in the context of gcc, if that is needed... ;-)
(Perhaps using git even is more fun than programming in C :-)

Personally, many things work fine for me using bugzilla and
the mailing list.  I just don't expect immediate replies
because of the current situation.

So can we get the attention of new possible contributors?
Or increase the activity of some of those who've been
contributing in the past?  So that a critical mass is
reached for a modern collaboration tool to be useful?

Cheers,
Harald


             reply	other threads:[~2022-12-08 21:27 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08 21:27 Harald Anlauf [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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

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='tmtkra$l49$1@ciao.gmane.io' \
    --to=anlauf@gmx.de \
    --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).