public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@Shaw.ca>
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 07:38:39 -0700	[thread overview]
Message-ID: <1ebd89f7-eeec-c019-0f2f-8d71afd0c602@Shaw.ca> (raw)
In-Reply-To: <Y/SLEH6/phijPZb4@calimero.vinschen.de>

On 2023-02-21 02:12, Corinna Vinschen wrote:
> 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.

Thanks Corinna,

That makes sense and I will see how I can tweak the FAQs to reflect the current 
status, likely X 12.6 refers to Cygwin 7.1, which makes that explicit statement.
I will make and send patches.

It is still worth getting licence agreements and updating and maintaining the 
CONTRIBUTORS file to acknowledge the copyright holders, and give the project a 
basis for contact in case there is ever any need to modify licences, or any 
other reason to contact copyright holders.
Without that list, the project can not contact copyright holders, so terms or 
licences can never change, if the current sources or licence(s) ever have 
problem(s) for any reason, so the project could have to reconstituted on some 
other basis, or else abandoned!

-- 
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

      reply	other threads:[~2023-02-21 14:38 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
2023-02-21 14:38   ` Brian Inglis [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=1ebd89f7-eeec-c019-0f2f-8d71afd0c602@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).