From: Charles Duffy <cduffy@spamcop.net>
To: xen-devel@lists.xensource.com
Subject: Re: Copyright/licensing info ?
Date: Wed, 14 Dec 2005 14:53:07 -0600 [thread overview]
Message-ID: <dnq0nl$64t$1@sea.gmane.org> (raw)
In-Reply-To: <20051214193100.GA23925@underhill.no-ip.org>
Sean Dague wrote:
> In the US everything caries implicit copyright. To ensure that something
> remains open source software, it needs to carry a license statement in that
> file. An external file referencing headers saying "Those files are under
> this license" isn't necessarily adequate.
I'm not a lawyer, and to the extent that I've had formal legal training
it focused on UCITA rather than intellectual property law, but I'm quite
certain that the below is correct:
The default case for a copyrighted work is that no license exists at
all, and thus all the actions regulated by copyright are prohibited
unless permission to take such actions is otherwise explicitly granted.
Granting a license to make use of a work otherwise does *not* require
that the license itself be referred to within the work -- the license
grant could be in an *entirely separate contract* negotiated between the
copyright holder and the licensee with no connection (in terms of being
packaged together) whatsoever.
Now, the copyright statement -- yes, you want that to be part of the
same document. As for the license, however, I'm quite certain that it
does not need to be the same document.
next prev parent reply other threads:[~2005-12-14 20:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 15:13 Copyright/licensing info ? B Thomas
2005-12-14 15:56 ` Keir Fraser
2005-12-14 18:35 ` Sean Dague
2005-12-14 19:02 ` Keir Fraser
2005-12-14 19:31 ` Sean Dague
2005-12-14 20:50 ` Karsten M. Self
2005-12-14 20:53 ` Charles Duffy [this message]
2005-12-14 21:13 ` Karsten M. Self
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='dnq0nl$64t$1@sea.gmane.org' \
--to=cduffy@spamcop.net \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.