From: David Edelsohn <dje.gcc@gmail.com>
To: Thomas Koenig <tkoenig@netcologne.de>,
"Zhang,
Cynthia X. (GSFC-710.0)[TELOPHASE CORP]"
<cynthia.x.zhang@nasa.gov>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: Inquiry: Country of Origin for gfortran
Date: Sun, 17 Jul 2022 12:04:52 -0400 [thread overview]
Message-ID: <CAGWvnynXNsyf3CDonSEA=zO_1aOzWsmiANUEk1W5weTrQ=FvKg@mail.gmail.com> (raw)
In-Reply-To: <a72955e2-7ff2-a3ad-d6e8-20d933a2b789@netcologne.de>
Should this question be posed to the Linux distribution that NASA is using?
Thanks, David
On Sun, Jul 17, 2022 at 4:56 AM Thomas Koenig via Gcc <gcc@gcc.gnu.org> wrote:
>
> Hi Cynthia,
>
> > Hello, my name is Cynthia and I am a Supply Chain Risk Management
> > Analyst at NASA. NASA is currently conducting a supply chain
> > assessment of gfortran. As stated in Sections 208 and 514 of the
> > Consolidated Appropriations Act, 2022, Public Law 117-103,
> > enacted March 15, 2022, a required step of our process is to
> > verify the Country of Origin (CoO) information for the
> > product (i.e., the country where the products were developed,
> > manufactured, and assembled.)
>
> > As gfortran is open source, we understand that this inquiry is
> > not directly applicable, as contributions may be made from
> > individuals from around the world. In this case, NASA is
> > interested in confirming the following information:
>
> > 1. Is there an organization which sponsors/publishes the project, or
> > a primary developer who audits the code for potential
> vulnerabilities, > errors, or malicious code? Y/N
>
> gfortran is not an independent project, it is part of the Gnu Compiler
> Collection, https://gcc.gnu.org/ . As such, any evaluation you
> may already have made of gcc also should also apply to gfortran,
> and I am also addressing this mail to the gcc mailing list, where
> it is more appropriate, especially since I personally am unclear
> about the current relationship with the Free Software Foundation.
>
> Regarding gfortran specifically: Code changes are reviewed by
> the individuals listed in the file
>
> https://gcc.gnu.org/git/?p=gcc.git;a=blob_plain;f=MAINTAINERS;hb=HEAD
>
> (where you can search for Fortran).
>
> > 2. Does gfortran have an overseeing organization or individual
> > along these lines? Y/N
>
> See my previous reply.
>
> > 1. If so, please provide the name of the organization and country
> > they are established in
>
> > If the information above is unknown or cannot be provided, we
> > request that you provide the country or list of countries where
> > the majority of contributions originate from to satisfy Sections
> > 208 and 514 of the Consolidated Appropriations Act, 2022, Public
> > Law 117-103, enacted March 15, 2022.
>
> Main contributions to gfortran, i.e. the Fortran front end to gcc and
> its supporting library, came (in no particular order) from the UK, the
> US, France, Finland, Germany, the Netherlands and the Czech Republic.
> Up to 2006, there were also some contributors from China.
>
> Best regards
>
> Thomas
>
next prev parent reply other threads:[~2022-07-17 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PH0PR09MB8537FABCA9ECD14246013F45D58B9@PH0PR09MB8537.namprd09.prod.outlook.com>
2022-07-17 8:55 ` Thomas Koenig
2022-07-17 16:04 ` David Edelsohn [this message]
2022-07-17 18:18 ` Richard Kenner
2022-07-17 19:26 ` Dave Blanchard
2022-07-17 20:13 ` Richard Kenner
2022-07-18 11:27 ` [EXTERNAL] " Zhang, Cynthia X. (GSFC-710.0)[TELOPHASE CORP]
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='CAGWvnynXNsyf3CDonSEA=zO_1aOzWsmiANUEk1W5weTrQ=FvKg@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=cynthia.x.zhang@nasa.gov \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--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).