Re: Reiser{3,4}: problem with the copyright statement

From: Zan Lynx
Date: Thu Nov 11 2004 - 21:22:18 EST

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.
> 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@xxxxxxx>

Attachment: signature.asc
Description: This is a digitally signed message part