From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from starfish.geekisp.com ([216.168.135.166]) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1PEptw-0000bD-Hg for openembedded-devel@lists.openembedded.org; Sat, 06 Nov 2010 22:02:17 +0100 Received: (qmail 32252 invoked by uid 1003); 6 Nov 2010 21:01:21 -0000 Received: from pool-96-240-180-126.ronkva.east.verizon.net (HELO ?192.168.1.167?) (philip@opensdr.com@96.240.180.126) by mail.geekisp.com with (DHE-RSA-AES256-SHA encrypted) SMTP; 6 Nov 2010 21:01:21 -0000 Message-ID: <4CD5C21F.2000006@balister.org> Date: Sat, 06 Nov 2010 17:01:19 -0400 From: Philip Balister User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101027 Fedora/3.1.6-1.fc13 Thunderbird/3.1.6 MIME-Version: 1.0 To: openembedded-devel@lists.openembedded.org References: <1288973274.28481.15978.camel@rex> In-Reply-To: X-SA-Exim-Connect-IP: 216.168.135.166 X-SA-Exim-Mail-From: philip@balister.org X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on discovery X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:20:07 +0000) X-SA-Exim-Scanned: Yes (on linuxtogo.org) Subject: Re: OpenEmbedded and the Yocto Project X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Nov 2010 21:02:18 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 11/06/2010 01:26 PM, Cliff Brake wrote: > On Fri, Nov 5, 2010 at 12:07 PM, Richard Purdie wrote: > >> So what do I mean by hard? First there are the conversations with your >> legal department where some questions arise: >> >> * How do you ensure license compliance? >> * When someone makes a change, how do you know the license is still >> correct? >> * You've mixing GPLv2 and v3? How are you ensuring no contamination? >> > > Is GPLv3 the issue here with patent, DMC, and Tivoization issues? Is > the solution to simply not have GPLv3 software in a device? > > Are there other license issues that companies are worried about? Cliff, I think each company has it's own licensing issues. The important thing for OE is to make sure our license fields are accurate. Philip