From: Jerry D <jvdelisle2@gmail.com>
To: Janne Blomqvist <blomqvist.janne@gmail.com>
Cc: gfortran <fortran@gcc.gnu.org>
Subject: Re: Team Collaboration Considerations
Date: Tue, 13 Dec 2022 04:22:34 -0800 [thread overview]
Message-ID: <23fe51c8-848c-6cfa-f188-bf76625f3fee@gmail.com> (raw)
In-Reply-To: <CAO9iq9GQTM=A_81o8e0XCfkeiyXOT050X4cuAUCQ099qANV4aQ@mail.gmail.com>
On 12/13/22 12:10 AM, Janne Blomqvist wrote:
--- snip --
>> Any thoughts from all?
>
> Hi,
>
> I haven't commented earlier as I haven't been active in GFortran
> development for a couple of years (new job, kids, etc. etc.). So don't
> take my opinions too seriously.
>
> But in general, yes, I do think IRC is showing its age in an
> increasingly multi-device and mobile world. From a Free Software
> perspective, adopting a closed platform like Slack is perhaps not
> ideal, if alternatives exist. And I believe the free (as in beer)
> version of Slack has some significant limitations compared to the
> licensed one. Matrix is perhaps the one with the most future
> potential, but maybe it's not really there yet. While I haven't used
> Mattermost myself, I've heard good things about it. And as long as
> it's not used as some sort of permanent record of things instead of
> the mailing list, I guess it's relatively easy to switch to another
> platform in the future. Just to be sure, this is some hosted version,
> and not something which Jerry must maintain himself on some server in
> a dusty corner?
>
> As for the perennial question of how to attract new contributors,
> yeah, it's hard. I'm happy to see that Harald has gotten off to a
> flying start, amazing! I also do note with some satisfaction that
> there's some good efforts to make modern Fortran attractive for
> developers, and not just something you use because the codebase you
> work on was started 4 decades ago. Gtk-Fortran was an early example of
> this which showed that modern Fortran could be useful outside the core
> numerics domain. I'm also thinking of the https://fortran-lang.org
> site and associated efforts like the 'stdlib', a more fleshed out
> 'standard' library (https://stdlib.fortran-lang.org/ ), and the
> package manager FPM (https://fpm.fortran-lang.org ). Keeping in touch
> with these people, and suggesting that people help that effort if they
> aren't comfortable with hacking on the compiler outright, could be a
> way of growing the open source Fortran programmer base, which could
> eventually grow into contributors to the compiler itself? In
> particular if they want to use some newfangled Fortran feature that
> doesn't work in GFortran; scratching your own itch is always a good
> motivator!
>
Hi Janne, great to hear from you and thanks for mentioning the efforts
of others.
Best regards,
Jerry
next prev parent reply other threads:[~2022-12-13 12:22 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 [this message]
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=23fe51c8-848c-6cfa-f188-bf76625f3fee@gmail.com \
--to=jvdelisle2@gmail.com \
--cc=blomqvist.janne@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).