Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759201AbXI0Syv (ORCPT ); Thu, 27 Sep 2007 14:54:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756351AbXI0Syi (ORCPT ); Thu, 27 Sep 2007 14:54:38 -0400 Received: from ug-out-1314.google.com ([66.249.92.171]:39287 "EHLO ug-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756295AbXI0Syg (ORCPT ); Thu, 27 Sep 2007 14:54:36 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:to:cc:subject:message-id:references:mime-version:content-type:content-disposition:in-reply-to:user-agent:from; b=cdK4IOitU7I1M/9ZyPPHY1aqjra2Dks14NwLoS0HDc8O4vGwWHZUFn4pWBQZ7WTTCO3xkijfxCgpq5mN9pMWnrgjBhzzWJ2xxAqEZkP/ZiTMR6N7xmis3/iDOgdzd8kT6aDPQyKDNdzuwcZsgMZ/RzNR1pBbSK6D55hI4PsNmO8= Date: Thu, 27 Sep 2007 22:54:29 +0400 To: "Luis R. Rodriguez" Cc: linux-wireless , linux kernel Subject: Re: New 'Changes-licensed-under' tag introduced for Linux-wireless Message-ID: <20070927185429.GA1748@martell.zuzino.mipt.ru> References: <43e72e890709271100n39f16c18x723dc7a85d418666@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43e72e890709271100n39f16c18x723dc7a85d418666@mail.gmail.com> User-Agent: Mutt/1.5.13 (2006-08-11) From: Alexey Dobriyan Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2765 Lines: 55 On Thu, Sep 27, 2007 at 02:00:09PM -0400, Luis R. Rodriguez wrote: > 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 Please, keep this tagged SFLC-waving somewhere out of mainline. Thank you. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/