[oe] OpenEmbedded and the Yocto Project

Tian, Kevin kevin.tian at intel.com
Sun Nov 7 07:26:27 UTC 2010


>From: Philip Balister
>Sent: Sunday, November 07, 2010 5:01 AM
>
>On 11/06/2010 01:26 PM, Cliff Brake wrote:
>> On Fri, Nov 5, 2010 at 12:07 PM, Richard Purdie<rpurdie at rpsys.net>  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?
>>> <cue a long discussion which I'd bet most companies have>
>>
>> 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.
>

Accurate and controllable so that you can easily come up a build which doesn't
contain sensitive licenses your customer are concerned and instead picks an
alternative serving same functionality if possible. :-)

Thanks
Kevin




More information about the Openembedded-devel mailing list