From: Zan Lynx <zlynx@acm.org>
To: Stephen Pollei <stephen_pollei@comcast.net>
Cc: Adrian Bunk <bunk@stusta.de>, Hans Reiser <reiser@namesys.com>,
linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: Reiser{3,4}: problem with the copyright statement
Date: Thu, 11 Nov 2004 19:08:12 -0700 [thread overview]
Message-ID: <1100225292.16114.27.camel@localhost> (raw)
In-Reply-To: <1100213504.8355.27.camel@fury>
[-- Attachment #1: Type: text/plain, Size: 2039 bytes --]
On Thu, 2004-11-11 at 14:51 -0800, Stephen Pollei wrote:
> On Thu, 2004-11-11 at 13:45, Adrian Bunk wrote:
> > If you add your code to governed files, and don't
> > want it to be owned by Hans Reiser, put your copyright label on that
> > code ... All portions of governed files not labeled otherwise are owned
> > by Hans Reiser, and ... and leaving the sentence in stating that
> > licensing is governed by the statement in this file, you accept this.
>
> > Besides the fact that giving the copyright completely away is nothing
> > that is legally possible in at least Germany, ...
>
> Han's method is also very likely nugatory within the USA.
>
> http://copyright.gov/title17/92chap2.html#204 clearly states that to
> transfer title of copyrighted work requires a written instrument of
> conveyance. That instrument of conveyance has to be signed and should in
> many ways look a lot like a deed or title for real estate -- ie. it must
> denote the boundaries of the transaction in a specific and explicit
> manner. In this instance it would probably be required to state in as
> unambiguous manner as possible which files and which versions this
> transfer is to cover. In the case of patches to preexisting files; it
> should also be specific as to which lines are to be covered unless one
> writes it in a style like a "Quit Claim Deed".
(not a lawyer, etc, etc. Just a LKML lurker.)
As I understand it, these things depend on the size of the changes. For
example, in the world of publishing, an editor may change spellings and
phrases, even add or remove entire paragraphs, but does not gain any
rights over the work by doing so.
If there was argument about this, deciding where the line is between a
edit and new work would be up to a court, no doubt. If I was deciding
it, changes to fit ReiserFS into a new VFS structure or fixing a locking
bug would be a "edit", while adding a new Reiser4 plugin or a more
efficient hash function would be "new work."
--
Zan Lynx <zlynx@acm.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-11-12 2:20 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 9:23 2.6.10-rc1-mm5 Andrew Morton
2004-11-11 10:09 ` 2.6.10-rc1-mm5 Magnus Damm
2004-11-11 10:11 ` 2.6.10-rc1-mm5 Andrew Morton
2004-11-11 10:24 ` 2.6.10-rc1-mm5 Magnus Damm
2004-11-11 10:45 ` 2.6.10-rc1-mm5 Brice Goglin
2004-11-11 11:00 ` 2.6.10-rc1-mm5 Stefano Rivoir
2004-11-11 11:13 ` 2.6.10-rc1-mm5 Andrew Morton
2004-11-11 11:04 ` 2.6.10-rc1-mm5 Markus Trippelsdorf
2004-11-11 11:08 ` 2.6.10-rc1-mm5 Andrew Morton
2004-11-11 21:55 ` 2.6.10-rc1-mm5 Martin J. Bligh
2004-11-11 22:14 ` 2.6.10-rc1-mm5 Andrew Morton
2004-11-12 9:27 ` 2.6.10-rc1-mm5 Jens Axboe
2004-11-11 22:41 ` 2.6.10-rc1-mm5 Andrew Morton
2004-11-12 10:50 ` [PATCH] Fix SHMEM options David Howells
2004-11-12 16:45 ` Christoph Hellwig
2004-11-11 12:11 ` 2.6.10-rc1-mm5: yenta_socket issue Rafael J. Wysocki
2004-11-11 12:21 ` Andrew Morton
2004-11-11 12:43 ` Rafael J. Wysocki
2004-11-12 3:55 ` Rusty Russell
2004-11-11 16:50 ` 2.6.10-rc1-mm5: REISER4_LARGE_KEY is still selectable Adrian Bunk
2004-11-12 7:07 ` Vladimir Saveliev
2004-11-12 13:23 ` Adrian Bunk
2004-11-12 16:16 ` DaMouse
2004-11-12 16:37 ` Vladimir Saveliev
2004-11-12 17:15 ` Adrian Bunk
2004-12-11 17:25 ` Hans Reiser
2004-11-11 21:45 ` Reiser{3,4}: problem with the copyright statement Adrian Bunk
2004-11-11 21:59 ` Linus Torvalds
2004-11-12 16:47 ` Christoph Hellwig
2004-11-12 17:06 ` Christoph Hellwig
2004-11-12 17:11 ` Adrian Bunk
2004-11-12 17:13 ` Christoph Hellwig
2004-11-12 19:33 ` Hans Reiser
2004-11-11 22:51 ` Stephen Pollei
2004-11-12 2:08 ` Zan Lynx [this message]
2004-11-11 23:28 ` 2.6.10-rc1-mm5: reiser4: print_clog in debug.c useless? Adrian Bunk
2004-11-12 2:39 ` 2.6.10-rc1-mm5: strange fs/reiser4/linux-5_reiser4_syscall.patch Adrian Bunk
2004-11-12 14:30 ` [patch] 2.6.10-rc1-mm5: some reiser4 cleanups Adrian Bunk
2004-11-12 19:00 ` 2.6.10-rc1-mm5 Alexander Nyberg
2004-11-13 0:11 ` 2.6.10-rc1-mm5 Greg KH
2004-11-13 17:55 ` 2.6.10-rc1-mm5 [u] Martin Schlemmer [c]
2004-11-13 21:16 ` Martin Schlemmer [c]
2004-11-13 21:22 ` Andrew Morton
2004-11-13 22:19 ` Jedi/Sector One
2004-11-13 22:22 ` Martin Schlemmer [c]
2004-11-13 23:24 ` Andrew Morton
2004-11-14 0:07 ` Martin Schlemmer [c]
2004-11-14 9:10 ` Jamie Lokier
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=1100225292.16114.27.camel@localhost \
--to=zlynx@acm.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=stephen_pollei@comcast.net \
--cc=torvalds@osdl.org \
/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