public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Damian Rouson <damian@sourceryinstitute.org>
To: Zaak Beekman <zbeekman@gmail.com>, fortran@gcc.gnu.org
Cc: "Andre Vehreschild" <vehre@gmx.de>,
	"Alessandro Fanfarillo" <elfanfa@ucar.edu>,
	"Rasmussen, Soren" <s.rasmussen@cranfield.ac.uk>
Subject: Re: [PATCH] Character length cleanup for Coarray Fortran library
Date: Sat, 10 Feb 2018 19:59:00 -0000	[thread overview]
Message-ID: <etPan.5a7f4f00.3cdbecef.33e3@sourceryinstitute.org> (raw)
In-Reply-To: <CAAbnBwYPbZVgmgOPTYOYv4n4iYYidUz0f+1qSDAazT4Zv6VnMQ@mail.gmail.com>

 


On February 10, 2018 at 11:25:58 AM, Zaak Beekman (zbeekman@gmail.com(mailto:zbeekman@gmail.com)) wrote:

> I have mostly dealt with the OpenCoarrays build system and various project  
> management/documentation/QA/CI and other administrivia and devops related  
> stuff---I am not *super* intimately familiar with the actual code base and  
> ABI. I am even less familiar with the GFortran inner workings.  


Same for me. I probably wrote less than 5% the C source code in OpenCoarrays.  Most of my time has been spent on the build system and documentation.

> Alessandro Fanfarillo and Andre are certainly more knowledgeable than I am in this area. 

The most sustainable approach is to integrate the building of OpenCoarrays and the running of the OpenCoarrays test suite into the gfortran development workflow and to consider the OpenCoarrays test results in the process for approving commits for trunk.  \

Andre’s time is mostly occupied by another project, and Alessandro just yesterday completed the postdoctoral position that funded his gfortran/OpenCoarrays work for the last ~2 years at NCAR.  On Monday, Alessandro will start a staff position at NCAR, but the staff position does not support any gfortran/OpenCoarrays work.  I am engaged in ongoing discussions with two NCAR researchers who have co-authored papers with Alessandro and me and I am hopeful that those researchers’ departments will fund some fraction of Alessandro’s time to work on gfortran and OpenCoarrays, but that is not yet certain.  

Over time, Cranfield University Ph.D. student Soren Rasmussen will be able to contribute.  Soren is in the first year of a 3-year fellowship funded by Sourcery Institute so some of his dissertation work will involve adding features to gfortran and OpenCoarrays.  I’m cc’ing Soren to ask if he might build and test Janne’s patch also.


Damian



  parent reply	other threads:[~2018-02-10 19:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1518284822.56399.ezmlm@gcc.gnu.org>
2018-02-10 19:25 ` Zaak Beekman
2018-02-10 19:35   ` Steve Kargl
2018-02-10 19:59   ` Damian Rouson [this message]
2018-02-10 21:07   ` Janne Blomqvist
2018-02-21 23:31 Dominique d'Humières
2018-02-21 23:39 ` Damian Rouson
  -- strict thread matches above, loose matches on Subject: below --
2018-02-09 16:11 Janne Blomqvist
2018-02-09 23:27 ` Steve Kargl
2018-02-10 19:34 ` Damian Rouson
2018-02-10 21:21   ` Janne Blomqvist
2018-02-21 19:35     ` Janne Blomqvist
2018-02-21 20:19       ` Damian Rouson
2018-02-21 20:56         ` Janne Blomqvist
2018-02-21 20:59           ` Izaak Beekman
2018-02-22  0:36           ` Damian Rouson
2018-02-22  9:46             ` Janne Blomqvist
2018-02-22  9:57               ` Janne Blomqvist

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=etPan.5a7f4f00.3cdbecef.33e3@sourceryinstitute.org \
    --to=damian@sourceryinstitute.org \
    --cc=elfanfa@ucar.edu \
    --cc=fortran@gcc.gnu.org \
    --cc=s.rasmussen@cranfield.ac.uk \
    --cc=vehre@gmx.de \
    --cc=zbeekman@gmail.com \
    /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).