public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Toon Moene <toon@moene.org>
To: "Holcomb, Katherine A (kah3f)" <kah3f@virginia.edu>,
	"sgk@troutmask.apl.washington.edu"
	<sgk@troutmask.apl.washington.edu>,
	Jerry D via Fortran <fortran@gcc.gnu.org>
Cc: Benson Muite <benson_muite@emailplus.org>
Subject: Re: Team Collaboration Considerations
Date: Fri, 9 Dec 2022 20:36:10 +0100	[thread overview]
Message-ID: <18de9467-4c7a-6c62-7423-431145bacc2f@moene.org> (raw)
In-Reply-To: <MN2PR13MB296049FC22BCB5EAE71ABED1921D9@MN2PR13MB2960.namprd13.prod.outlook.com>

On 12/8/22 20:14, Holcomb, Katherine A (kah3f) via Fortran wrote:

> I was thinking I might try to contribute when I retire, though that may be in a year or two.  But it's been a very long time since I dove into a large software project and it's intimidating.  I do know C (really C++, I haven't used plain C for a long time).   I am one of those "aging" types but I am familiar at least superficially with newer tools because I must use them for work, specifically git and Slack (Mattermost seems to be an open-source Slack alternative) -- we make heavy use of Slack in particular.
> 
> Is there some kind of "getting started" guide?

Thanks, Katherine, for your thoughts on this side of support (i.e., 
fixing compiler bugs, and how to get people interested in contributing).

Based on that, I thought of another approach, namely: interesting 
*users* of gfortran to provide us with useful information on their 
experiences with it (lest we only look at the depressing list of PRs).

Would it help if we created a fortran-help@gcc.gnu.org list (a loose 
parallel of gcc-help@gcc.gnu.org) for *questions* from our user base ?

I just have to look at the questions I get at work from my colleagues:

1. I get this message while compiling XYZ weather forecasting model
    (HELP, what does it mean ?). How do I solve it ? Do I need ABC
    (mega-corporation chip manufacturing's) fortran compiler ?

2. gfortran gives me a "internal compiler error", but this code
    compiled perfectly just a year ago (an ICE is never a user's
    problem). How can I work around it ?

3. Is this (source code provided) code conformant ? gfortran
    complains about it, but XYZ compiler just compiles it fine.

etc.

This might not result in many new contributors, but it shows to the 
broader GCC development community what gfortran is used for, and how 
*we* deal with their questions and problems (and, thus, how important 
this part of the GNU Compiler *Collection* is).

Oh, BTW, I retire in nine months, which would give me loads of time to 
deal with such a mailing list.

Kind regards,

-- 
Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands


  reply	other threads:[~2022-12-09 19:36 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 [this message]
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=18de9467-4c7a-6c62-7423-431145bacc2f@moene.org \
    --to=toon@moene.org \
    --cc=benson_muite@emailplus.org \
    --cc=fortran@gcc.gnu.org \
    --cc=kah3f@virginia.edu \
    --cc=sgk@troutmask.apl.washington.edu \
    /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).