public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andre Vehreschild <vehre@gmx.de>
To: Benson Muite <benson_muite@emailplus.org>
Cc: Damian Rouson <damian@archaeologic.codes>,
	Thomas Koenig <tkoenig@netcologne.de>,
	Jerry D <jvdelisle2@gmail.com>,
	Mikael Morin <morin-mikael@orange.fr>,
	Paul Richard Thomas <paul.richard.thomas@gmail.com>,
	GCC-Fortran-ML <fortran@gcc.gnu.org>,
	Lexi Pimenidis <lexi@badgersystems.de>
Subject: Re: Possible funding of gfortran work
Date: Mon, 5 Jun 2023 12:07:07 +0200	[thread overview]
Message-ID: <20230605120707.3a0929d8@vepi2> (raw)
In-Reply-To: <82fbd0b2-41d9-c2b7-1655-816d5681c7c4@emailplus.org>

Hi Benson,

thank you for your input. Comments are inline:

> Maybe add Quantum Espresso:
> https://www.quantum-espresso.org/

done

> R and Octave may also be good examples of use cases.

Mhhh, both are not written in Fortran, right? I don't feel tempted to
include other programming languages into the references list. It feels odd to
me. Any thoughts, anyone?


> Some gfortran work has been done as company sponsored in that
> individuals using the compiler needed it for company work and could work
> on the compiler on company time.  If a large proportion is voluntary and
> companies only sponsor small extensions and bug fixes, one might assume
> that if the funding is given, once it is finished, the chances of
> further work will be very limited.  Maybe one can tie into the GNU
> compiler collection as well, emphasizing the longevity of the project
> and usefulness of the funding in adding additional capabilities and
> cleaning up code contributions. Then indicate that new parts that this
> proposal addresses have primarily been voluntary because they are not
> yet ready for production use, and this project would make them ready for
> production use so that in future maintenance efforts can be made by the
> community (both voluntary and sponsored).

I have added a paragraph about sponsoring of general gfortran work:

GFortran in general stems from a merge of projects that have been supported by
academic research, commercial needs and in large parts volunteers. Funding by
companies was mostly done by allowing employees to work on features required for
the company and donating the code.

Is that what you were trying to add?

Regards,
	Andre
--
Andre Vehreschild * Email: vehre ad gmx dot de

  parent reply	other threads:[~2023-06-05 10:07 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
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 [this message]
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=20230605120707.3a0929d8@vepi2 \
    --to=vehre@gmx.de \
    --cc=benson_muite@emailplus.org \
    --cc=damian@archaeologic.codes \
    --cc=fortran@gcc.gnu.org \
    --cc=jvdelisle2@gmail.com \
    --cc=lexi@badgersystems.de \
    --cc=morin-mikael@orange.fr \
    --cc=paul.richard.thomas@gmail.com \
    --cc=tkoenig@netcologne.de \
    /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).