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

[Adrian Bunk]

Hi Hans,

both the reiser3 and reiser4 copyright statements contain:

<--  snip  -->

Reiser4 is hereby licensed under the GNU General
Public License version 2.

Source code files that contain the phrase "licensing governed by
reiser4/README" are "governed files" throughout this file.  Governed
files are licensed under the GPL.  The portions of them owned by Hans
Reiser, or authorized to be licensed by him, have been in the past,
and likely will be in the future, licensed to other parties under
other licenses.  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 so the poor blight and his customers can keep things straight.
All portions of governed files not labeled otherwise are owned by Hans
Reiser, and by adding your code to it, widely distributing it to
others or sending us a patch, and leaving the sentence in stating that
licensing is governed by the statement in this file, you accept this.
...

<--  snip  -->


I have no problem with dual-licensed code, but I do strongly dislike 
having this "unlike you explicitley state otherwise, you transfer all 
rights to Hans Reiser" in the kernel.

Besides the fact that giving the copyright completely away is nothing 
that is legally possible in at least Germany, I'm not happy with having 
to check every single file in the source tree for additional licence 
clauses before editing it - and then to consider whether my contribution 
might deserve a copyright label according to my local law.


cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/