linux-kernel - New 'Changes-licensed-under' tag introduced for Linux-wireless

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 27 Sep 2007 14:00:09 -0400
From:	"Luis R. Rodriguez" <mcgrof@...il.com>
To:	linux-wireless <linux-wireless@...r.kernel.org>
Cc:	"linux kernel" <linux-kernel@...r.kernel.org>
Subject: New 'Changes-licensed-under' tag introduced for Linux-wireless

Our guidelines for patches [1] for Linux-wireless has been updated.
One section asks Linux-wireless developers to subscribe to the patch
guideline wiki page (section 2) and another which introduces the new
'Changes-licensed-under' (section 10).

Here I'll cover the new 'Changes-licensed-under' tag but please refer
to the link and subscribe to the page for the complete details and for
further changes.

--

Based on the new guidelines posted by the SFLC on ''Maintaining
Permissive-Licensed Files in a GPL-Licensed Project: Guidelines for
Developers'' [2], specifically section 5, we are introducing a new tag
for use with patches which deal with files licensed under permissive
licenses (BSD, ISC) on Linux wireless in our larger GPL project, the
Linux kernel. The tag is Changes-licensed-under and can be used by
developers to clarify the intended license for their patch on
permissive licensed files. It is clear that not all changes qualify a
patch author for Copyright but a lot of patches do qualify an author
for copyright. If you want crystal clear details of what constitutes
as a copyrightable change, at least within the US and the EU, you can
refer to SFLC's ''Originality Requirements under U.S. and E.U.
Copyright Law'' [3].

Although some developers have a practice of implying their patches for
a permissive licensed file abides by the respective permissive license
of the file being patched, and although some changes are obviously not
copyrightable, we would like to ''err on the side of caution'', take
the advice from SFLC, and introduce Changes-licensed-under in order to
help the BSD family reap benefits of our contributions to permissive
licensed files.

The Changes-licensed-under tag should be put before the Signed-off-by
tag. Since this tag is used to cover changes under permissive licenses
example of possible licenses are 3-Clause-BSD, and ISC. If you are
making changes to multiple permissive licensed files then please
specify which license covers what files.

--

For examples of using this tag please refer to the guidelines.

[1] http://linuxwireless.org/en/developers/SubmittingPatches
[2] http://www.softwarefreedom.org/resources/2007/gpl-non-gpl-collaboration.html
[3] http://www.softwarefreedom.org/resources/2007/originality-requirements.html

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