From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from moene.org (84-86-97-173.fixed.kpn.net [84.86.97.173]) by sourceware.org (Postfix) with ESMTPS id D26D63858421 for ; Fri, 9 Dec 2022 19:36:15 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org D26D63858421 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=moene.org Authentication-Results: sourceware.org; spf=none smtp.mailfrom=moene.org Received: from localhost ([127.0.0.1]) by moene.org with esmtp (Exim 4.96) (envelope-from ) id 1p3jAI-009vz4-0U; Fri, 09 Dec 2022 20:36:10 +0100 Message-ID: <18de9467-4c7a-6c62-7423-431145bacc2f@moene.org> Date: Fri, 9 Dec 2022 20:36:10 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Subject: Re: Team Collaboration Considerations To: "Holcomb, Katherine A (kah3f)" , "sgk@troutmask.apl.washington.edu" , Jerry D via Fortran Cc: Benson Muite References: <6e48ab2c-f006-c57f-db39-2b3efb6b30a4@gmail.com> Content-Language: en-US From: Toon Moene Organization: Moene Computational Physics, Maartensdijk, The Netherlands In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.0 required=5.0 tests=BAYES_00,KAM_DMARC_STATUS,KAM_LAZY_DOMAIN_SECURITY,KHOP_HELO_FCRDNS,NICE_REPLY_A,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: 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