On 9/19/05, Warren Turkal <[EMAIL PROTECTED]> wrote:
> On Sunday 18 September 2005 09:49 pm, Timothy Miller wrote:
> > I think there are jurisdictions where it's difficult or impossible for
> > someone to sign over the copyright.
> 
> If that is the case, then how will you also license under a proprietary
> license? In order to transfer a copyright in the US, like what would have to
> be done for you to have a second proprietary license, you have to have a
> written instrument that defines what is transferred.
> 
> You would probably be better off sticking with vanilla LGPL in the case you
> speak, as you could still use the code in a proprietary product as long as
> you provide the source for any LGPL modules. You would just need to make sure
> to have well defined separation between the different modules so that they
> could be used like shared libs in an OS.

It is not MY use of the LGPL code that I'm trying to protect.  In
order to have a full product line, I have to be able to license a copy
of the IP to someone else who does not want to be bound by (L)GPL.  In
fact, MOST customers who license the IP will not want to be bound by
the IP.  Instead, however, they would be willing to be bound by other
non-disclosure terms.

We have to be able to do it this way in order to get the sort of
revenue we need to be a successful company.  A long time ago, we
figured out that there probably just are not enough open source users
who would be interested in buying this card.  We hope to be wrong, but
in order to ensure that we can sell enough, we decided that our
primary target is embedded systems.  That means we will get most of
our revenue from chips, not boards, and from licensing IP.  This
doesn't compromise our comittment to free software (free software
users dictate our specs), and it allows open source users to benefit
from the economy of scale.

_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)

Reply via email to