From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Cc: "Watson,
Christian M. (GRC-V000)[Peerless Technologies Corp.]"
<christian.m.watson@nasa.gov>,
"Pesich, Justin M. (GRC-LTF0)" <justin.m.pesich@nasa.gov>
Subject: Re: Country Of Origin Verification - 8944
Date: Wed, 17 Jun 2020 21:16:56 -0600 [thread overview]
Message-ID: <b7e4732d-e694-2539-1d00-d297d02f2f76@SystematicSw.ab.ca> (raw)
In-Reply-To: <6edd8c67-2558-783b-6766-8bc684cd1f4b@SystematicSw.ab.ca>
On 2020-06-11 11:19, Brian Inglis wrote:
> On 2020-06-11 09:59, Watson, Christian M. (GRC-V000)[Peerless Technologies
> Corp.] via Cygwin wrote:
>> My name is Christian Watson and I am a Supply Chain Risk Management Coordinator at NASA Glenn Research Center As such, I ensure that all NASA Headquarter IT purchase requests comply with Section 514 of the Consolidated Appropriations Act, 2018, Public Law 115-141 (amended), enacted February 28, 2018. To do so, the country of origin information must be obtained from the company that develops, produces, manufactures, or assembles the product(s). Specifically, identify the country where each of the following products were developed, manufactured, and assembled:
Just checked the basis of what you are asking.
Section 514 is about use of funds for acquisition:
Cygwin is free software so these criteria *do not apply*!
Products were developed and assembled by an international project team.
If you are spending funds to acquire this software, ask the people who you are
paying for a free product to provide the answers!
If in doubt, see what answers are in the files for Linux, NTP, or similar projects.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-06-18 3:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 15:59 Watson, Christian M. (GRC-V000)[Peerless Technologies Corp.]
2020-06-11 17:19 ` Brian Inglis
2020-06-17 15:37 ` [EXTERNAL] " Watson, Christian M. (GRC-V000)[Peerless Technologies Corp.]
2020-06-17 17:56 ` Bill Stewart
2020-06-17 18:04 ` Andrey Repin
2020-06-17 19:21 ` Marco Atzeri
2020-06-18 0:14 ` Brian Inglis
2020-06-18 0:44 ` [cygwin] " Jason Pyeron
2020-06-18 2:59 ` Brian Inglis
2020-06-18 3:17 ` Jason Pyeron
2020-06-18 3:16 ` Brian Inglis [this message]
2020-06-11 16:07 Watson, Christian M. (GRC-V000)[Peerless Technologies Corp.]
2020-06-11 17:24 ` Brian Inglis
2020-06-14 15:43 ` Christopher Faylor
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=b7e4732d-e694-2539-1d00-d297d02f2f76@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=christian.m.watson@nasa.gov \
--cc=cygwin@cygwin.com \
--cc=justin.m.pesich@nasa.gov \
/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).