From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: Cygwin Patches <cygwin-patches@cygwin.com>
Subject: Copyright outdated? in Cygwin/X FAQ 12.6 and not addressed in Cygwin FAQ 7.1 link
Date: Mon, 20 Feb 2023 13:20:16 -0700 [thread overview]
Message-ID: <6b01a995-96e5-7b46-3323-1cf348d25252@Shaw.ca> (raw)
Hi folks,
[Addressing to patches as that's where we'll fix it, and not a general issue.]
Noticed that:
https://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-copyright-cygwin
"12.6. Who holds the copyright on the Cygwin source code?
Red Hat owns the copyright on the Cygwin source code. Red Hat requires that
copyright be assigned to Red Hat for non-trivial changes to Cygwin. You must
fill out a copyright transfer form if you are going to contribute substantial
changes to Cygwin."
Has that not been assigned to the project?
And also:
https://cygwin.com/faq/faq.html#faq.what.copyright
"7.1. What are the copyrights?
7.1.
What are the copyrights?
Please see https://cygwin.com/licensing.html for more information about Cygwin
copyright and licensing."
->
"Cygwin™ Linking Exception
As a special exception, the copyright holders of the Cygwin library"
Is that the project?
Or does it belong to the authors individually and/or the project or the "Cygwin
authors" collectively?
Could we please be as current and explicit as possible in the FAQs once current
situation is clear and wording is agreed?
Thinking that Cygwin/X FAQ 12.6 should defer to Cygwin FAQ 7.1.
Willing to submit FAQ patches ;^>
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next reply other threads:[~2023-02-20 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 20:20 Brian Inglis [this message]
2023-02-20 22:00 ` Jon Turney
2023-02-20 22:57 ` Brian Inglis
2023-02-21 9:12 ` Corinna Vinschen
2023-02-21 14:38 ` 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=6b01a995-96e5-7b46-3323-1cf348d25252@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin-patches@cygwin.com \
/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).