From: Thomas Koenig <tkoenig@netcologne.de>
To: Jerry D <jvdelisle2@gmail.com>, gfortran <fortran@gcc.gnu.org>
Subject: Re: Possible funding of gfortran work
Date: Sat, 27 May 2023 10:08:56 +0200 [thread overview]
Message-ID: <737bbf36-04a8-c1e4-b3aa-31121df66013@netcologne.de> (raw)
In-Reply-To: <0d923990-0b7a-a1ea-8389-bf3837e73ed0@gmail.com>
On 26.05.23 23:22, Jerry D via Fortran wrote:
> Sorry about my messages getting chopped.
>
> On 5/25/23 9:34 PM, Jerry DeLisle via Fortran wrote:
>> Hi all,
>>
>> I found this message in my spam folder tonight.
>>
>> Please look. I also sent a note to Damian on this.
>>
>> Maybe we can get someone to push forward on te native coarrays work?
I think the native coarrays are a good field. General bug fixing would
also be a good idea.
[quoting for the mail]
> I would like to discuss with the GFortran developer community whether
> there is interest to setup a joint project to pay somebody to work on
> GFortran full time. We have funding available for 18 months with 600k
> EUR starting mid of June (please do not share this numbers publicly
> yet), but we can also ask the fund for more money if needed. What do you
> think? Is it worth to bring this up on the GFortran mailing list or
> mattermost server?
It is really good so finally see a source of gfortran funding.
For hiring somebody full-time for a year, I am not sure who would be
available full-time, I think most people who have experience working
on gfortran have other commitments. We would have to see if somebody
has the free time.
What would be great would be a possibility for people to work on
an hourly basis on certain, well-defined projects. This is probably
something that contributors could fit in much better, and would provide
an additional incentive to take up gfortran work again :-)
Do you know if this is, in fact, a possibility?
Best regards
Thomas
next prev parent reply other threads:[~2023-05-27 8:09 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 4:34 Jerry DeLisle
2023-05-26 17:09 ` Bernhard Reutner-Fischer
2023-05-26 21:22 ` Jerry D
2023-05-27 8:08 ` Thomas Koenig [this message]
2023-05-27 11:24 ` Andre Vehreschild
2023-05-27 16:19 ` Paul Richard Thomas
2023-05-28 14:26 ` Nicolas König
2023-05-28 15:07 ` Thomas Koenig
2023-05-28 19:25 ` Mikael Morin
2023-05-28 20:53 ` Jerry D
2023-05-30 13:32 ` Andre Vehreschild
2023-05-30 20:08 ` Thomas Koenig
2023-05-31 3:46 ` Benson Muite
2023-05-31 6:08 ` Thomas Koenig
2023-05-31 8:42 ` Benson Muite
2023-05-31 12:23 ` Andre Vehreschild
2023-05-31 14:08 ` Damian Rouson
2023-06-01 9:18 ` Andre Vehreschild
2023-06-01 10:56 ` Bernhard Reutner-Fischer
2023-06-01 10:59 ` Mikael Morin
2023-06-04 8:23 ` Thomas Koenig
2023-06-05 8:08 ` Andre Vehreschild
2023-06-05 11:44 ` Mikael Morin
2023-06-06 13:06 ` Andre Vehreschild
2023-06-08 12:38 ` Mikael Morin
2023-06-14 8:28 ` Andre Vehreschild
2023-06-14 9:40 ` Mikael Morin
2023-06-14 18:48 ` Bernhard Reutner-Fischer
2023-06-01 11:12 ` Benson Muite
2023-06-04 7:49 ` Thomas Koenig
2023-06-05 10:12 ` Andre Vehreschild
2023-06-05 10:07 ` Andre Vehreschild
2023-06-05 12:16 ` Thomas Koenig
2023-06-05 12:21 ` Andre Vehreschild
2023-06-08 5:34 ` Benson Muite
2023-06-14 8:00 ` Andre Vehreschild
2023-06-02 0:53 ` Jerry D
2023-06-05 10:09 ` Andre Vehreschild
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=737bbf36-04a8-c1e4-b3aa-31121df66013@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=jvdelisle2@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).