From: Jerry D <jvdelisle2@gmail.com>
To: gfortran <fortran@gcc.gnu.org>
Subject: Re: Possible funding of gfortran work
Date: Fri, 26 May 2023 14:22:21 -0700 [thread overview]
Message-ID: <0d923990-0b7a-a1ea-8389-bf3837e73ed0@gmail.com> (raw)
In-Reply-To: <4697f7be-ac3e-8c5d-f27c-3aec89b5b03f@protonmail.com>
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?
>
> Other thoughts?
>
> Jerry
>
[awvwgk] awvwgk Regular
May 16
Hi Jerry,
we are currently securing funding for the Fortran community from the
German government, see this thread:
Application to the Sovereign Tech Fund Projects
We recently had a meeting in Berlin with the Sovereign Tech Fund
(STF) to evaluate the pilot round of their open source funding program
which our community participated in. A big thanks to the people in who
worked on the projects in our community. Now with the pilot round coming
to an end soon, we have the chance to apply for further funding with the
STF. Let’s have a look through our community and identity the projects
with the largest impact on Fortran. A couple of suggestions to get the …
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?
Best,
Sebastian
Visit Message or reply to this email to respond to awvwgk.
next prev parent reply other threads:[~2023-05-26 21:22 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 [this message]
2023-05-27 8:08 ` Thomas Koenig
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=0d923990-0b7a-a1ea-8389-bf3837e73ed0@gmail.com \
--to=jvdelisle2@gmail.com \
--cc=fortran@gcc.gnu.org \
/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).