From: Jerry D <jvdelisle2@gmail.com>
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>, Harald Anlauf <anlauf@gmx.de>
Subject: Re: Team Collaboration Considerations
Date: Sat, 10 Dec 2022 12:10:20 -0800 [thread overview]
Message-ID: <72136797-c9d4-7225-8b82-1dcac38684e8@gmail.com> (raw)
In-Reply-To: <MN2PR13MB296049FC22BCB5EAE71ABED1921D9@MN2PR13MB2960.namprd13.prod.outlook.com>
On 12/8/22 11:14 AM, 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?
>
> Katherine Holcomb
> UVA Research Computing https://www.rc.virginia.edu
> kah3f@virginia.edu 434-982-5948
>
In your case I would recommend just pick a bug and start exploring it
with gdb and valgrind. There is no need to learn the whole project. If
you want, we could pick one for you as a starter. I will send you an
invite to the Mattermost so you can watch as we organize it. One
thought we had is to use "boards" for categories of bugs and use it as a
way to triage the list of bugs (ideas evolving)
I dont think you need to wait for retirement. Nothing wrong with
dabbling hear and there as time permits.
next prev parent reply other threads:[~2022-12-10 20:10 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 [this message]
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=72136797-c9d4-7225-8b82-1dcac38684e8@gmail.com \
--to=jvdelisle2@gmail.com \
--cc=anlauf@gmx.de \
--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).