From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OpenEmbedded and the Yocto Project
Date: Sat, 06 Nov 2010 17:01:19 -0400 [thread overview]
Message-ID: <4CD5C21F.2000006@balister.org> (raw)
In-Reply-To: <AANLkTi=9baSJYxwULah-FNS50gaK9bhF=aBG-4-ChrrP@mail.gmail.com>
On 11/06/2010 01:26 PM, Cliff Brake wrote:
> On Fri, Nov 5, 2010 at 12:07 PM, Richard Purdie<rpurdie@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.
Philip
next prev parent reply other threads:[~2010-11-06 21:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 16:07 OpenEmbedded and the Yocto Project Richard Purdie
2010-11-05 16:36 ` Paul Menzel
2010-11-05 19:24 ` Richard Purdie
2010-11-05 20:45 ` Frans Meulenbroeks
2010-11-05 16:37 ` Chris Larson
2010-11-06 17:26 ` Cliff Brake
2010-11-06 17:44 ` Stefan Schmidt
2010-11-06 21:01 ` Philip Balister [this message]
2010-11-07 7:26 ` Tian, Kevin
-- strict thread matches above, loose matches on Subject: below --
2010-11-02 14:16 Philip Balister
2010-11-02 14:42 ` Koen Kooi
2010-11-02 19:55 ` Scott Garman
2010-11-02 22:00 ` Leon Woestenberg
2010-11-02 22:11 ` Scott Garman
2010-11-02 22:24 ` Richard Purdie
2010-11-02 22:44 ` Khem Raj
2010-11-03 9:09 ` Petr Štetiar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CD5C21F.2000006@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.