From: Jerry D <jvdelisle2@gmail.com>
To: gfortran <fortran@gcc.gnu.org>
Subject: Team Collaboration Considerations
Date: Sat, 3 Dec 2022 19:52:56 -0800 [thread overview]
Message-ID: <6e48ab2c-f006-c57f-db39-2b3efb6b30a4@gmail.com> (raw)
Hi all,
Some of you may recall way back when I established the gfortran IRC
channel to facilitate collaboration on gfortran development.
I have had some discussions with a few people about advancing to newer
technology. One thing I have learned is that the gcc C++ team has
adopted the Mattermost platform. I have also used Slack and Teams.
There are many others. The gcc IRC channel is still active. The gfortran
IRC channel exists but is less used.
I would like suggest that gfortranners adopt one of these platforms. The
advantages are:
1. We can post chat questions back and forth via mobile devices
without having toopen and scan our emails
2. We can share examples and files easily.
3. Screen shot are easily exchanged.
4. Integration with platforms such as Github.
Pros and Cons of some of the choices. I have only looked at the Free
options
1. Slack has adopted some limitations on being able to go back and look
at older posts. Functionally it is quite good and integrates well
with github.
2. I looked at Element and Fractal which use the Matrix protocols.
Very open source, not so mature yet.
3. Mattermost looks pretty good and was easy to set up. The free
version is a bit better than Slacks. GCC C++ uses it.
If we can get a concensus I would happy to get something set up . I am
leaning to Mattermost. The mobile phone app is easy and the web browser
works fine.
I do think in the long run, doing this will help everyone greatly.
Any thoughts from all?
Regards,
Jerry
next reply other threads:[~2022-12-04 3:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 3:52 Jerry D [this message]
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
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=6e48ab2c-f006-c57f-db39-2b3efb6b30a4@gmail.com \
--to=jvdelisle2@gmail.com \
--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).