public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Zhang, Cynthia X. (GSFC-710.0)[TELOPHASE CORP]" <cynthia.x.zhang@nasa.gov>
To: Thomas Koenig <tkoenig@netcologne.de>,
	"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	gcc mailing list <gcc@gcc.gnu.org>
Subject: RE: [EXTERNAL] Re: Inquiry: Country of Origin for gfortran
Date: Mon, 18 Jul 2022 11:27:47 +0000	[thread overview]
Message-ID: <PH0PR09MB8537C1F60D0F3E1BD7B3C8F3D58C9@PH0PR09MB8537.namprd09.prod.outlook.com> (raw)
In-Reply-To: <a72955e2-7ff2-a3ad-d6e8-20d933a2b789@netcologne.de>

Thank you for your help!

-----Original Message-----
From: Thomas Koenig <tkoenig@netcologne.de> 
Sent: Sunday, July 17, 2022 4:55 AM
To: Zhang, Cynthia X. (GSFC-710.0)[TELOPHASE CORP] <cynthia.x.zhang@nasa.gov>; fortran@gcc.gnu.org; gcc mailing list <gcc@gcc.gnu.org>
Subject: [EXTERNAL] Re: Inquiry: Country of Origin for gfortran


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://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgcc.gnu.org%2F&amp;data=05%7C01%7Ccynthia.x.zhang%40nasa.gov%7C6cc48038caed4c1e908a08da67d211b3%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637936449313898438%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=NxQtCichrdJBdyRR6ZIlmttE72yqSXE6rIxWUEQoMHQ%3D&amp;reserved=0 .  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://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgcc.gnu.org%2Fgit%2F%3Fp%3Dgcc.git%3Ba%3Dblob_plain%3Bf%3DMAINTAINERS%3Bhb%3DHEAD&amp;data=05%7C01%7Ccynthia.x.zhang%40nasa.gov%7C6cc48038caed4c1e908a08da67d211b3%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637936449313898438%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=PUhKlistyKpWB%2BvknwbesKHucw3uohnDMBqL66%2BrVkI%3D&amp;reserved=0

(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


      parent reply	other threads:[~2022-07-18 11:27 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
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   ` Zhang, Cynthia X. (GSFC-710.0)[TELOPHASE CORP] [this message]

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=PH0PR09MB8537C1F60D0F3E1BD7B3C8F3D58C9@PH0PR09MB8537.namprd09.prod.outlook.com \
    --to=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).