From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: Copyright outdated? in Cygwin/X FAQ 12.6 and not addressed in Cygwin FAQ 7.1 link
Date: Tue, 21 Feb 2023 10:12:48 +0100 [thread overview]
Message-ID: <Y/SLEH6/phijPZb4@calimero.vinschen.de> (raw)
In-Reply-To: <6b01a995-96e5-7b46-3323-1cf348d25252@Shaw.ca>
On Feb 20 13:20, Brian Inglis wrote:
> 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?
Yes, that's the Cygwin project, not the distro as a whole. All packages
in the distro have their own license. THe above is strictly only about
the Cygwin project license as defined by ...
> [...]
> Or does it belong to the authors individually and/or the project or the
https://cygwin.com/git/?p=newlib-cygwin.git;a=blob;f=winsup/CYGWIN_LICENSE
After Red Hat stopped selling the Cygwin buyout license, Red Hat changed
the license of the DLL to "GPLv3+ w/ linking exception" and handed the
copyright over to the community, so the copyright holders are the
individual contributors, most of which are mentioned in
https://cygwin.com/git/?p=newlib-cygwin.git;a=blob;f=winsup/CONTRIBUTORS
The former buyout licenses had a pretty long lifetime, so it was
necessary from a legal perspective, that contributors passed over the
code under a BSD-2-clause license as long as the buyout licenses were
active. This time has passed in the meantime, so we don't really need
the CONTRIBUTORS file anymore.
> "Cygwin authors" collectively?
The project doesn't "belong" anybody anymore. The project has copyright
holders. Those are the developers contributing code to the project
collectively.
Corinna
next prev parent reply other threads:[~2023-02-21 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 20:20 Brian Inglis
2023-02-20 22:00 ` Jon Turney
2023-02-20 22:57 ` Brian Inglis
2023-02-21 9:12 ` Corinna Vinschen [this message]
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=Y/SLEH6/phijPZb4@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).