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: [EXTERNAL] Re: Country Of Origin Verification - 8944
Date: Wed, 17 Jun 2020 18:14:27 -0600 [thread overview]
Message-ID: <c50f370f-6797-16af-e3b2-73e55e35c7e0@SystematicSw.ab.ca> (raw)
In-Reply-To: <bdc83ef9-474e-1cda-8a23-43b905d848a1@gmail.com>
On 2020-06-17 13:21, Marco Atzeri via Cygwin wrote:
> On 17.06.2020 17:37, Watson, Christian M. (GRC-V000)[Peerless Technologies
> Corp.] via Cygwin wrote:
>> We appreciate the reply. We are looking to use this software on a NASA
>> facility and that is why we sent you the questions we did to comply with our
>> security restrictions. If you could tell us where this software originated
>> from that would be all we need to move forward. We have followed the link you
>> suggested and could still not find this information.
> To make easy for you, as I did for Octave some time ago:
> https://en.wikipedia.org/wiki/Cygwin
> Cygwin was originally developed by Cygnus Solutions, which was later acquired by
> Red Hat (now part of IBM).
> https://en.wikipedia.org/wiki/Cygnus_Solutions
> So the original authors were located in USA.
> Also the main server is currently located in USA.
Cygwin DLL current maintainers and contributors:
https://cygwin.com/git/?p=newlib-cygwin.git;a=blob;f=winsup/CONTRIBUTORS;hb=HEAD
Cygwin packages current maintainers:
https://cygwin.com/cygwin-pkg-maint
To get all Cygwin package maintainers, you would have to download the package
archives from https://sourceware.org/pipermail/cygwin-announce/1997-May.txt.gz
thru to the current archive
https://cygwin.com/pipermail/cygwin-announce/2020-June.txt.gz, unzip them all,
and get the senders of each announcement.
For a package's country of origin, you would have to check with whom, and from
where the source code for the package originated.
Newlib (Cygwin libc) current maintainers:
https://cygwin.com/git/?p=newlib-cygwin.git;a=blob;f=newlib/MAINTAINERS;hb=HEAD
To get all Cygwin and Newlib contributors, you would have to clone the
repository at top, list the log, and get the authors of each change.
You should also be aware that Cygwin and Newlib have incorporated source code
from various BSD systems: FreeBSD, NetBSD, OpenBSD.
--
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 0:14 UTC|newest]
Thread overview: 11+ 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 [this message]
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
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=c50f370f-6797-16af-e3b2-73e55e35c7e0@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).