linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Patrick Laplante" <plaplante@vanteon.com>
To: <bluez-users@lists.sourceforge.net>
Subject: RE: [Bluez-users] Question about licensing!
Date: Sat, 25 Mar 2006 18:55:30 -0500	[thread overview]
Message-ID: <E1FNIbj-0004oU-50@mail.sourceforge.net> (raw)
In-Reply-To: <000901c65064$040843c0$6280a8c0@clytemnestra>

My customer makes reference board.  So they will sell that solution
(firmware and board) to other customers that will then customize, rewrite,
do whatever they want with it to then sell their product to the consumer
market.

With that in mind, my customer is hiring me to write reference code
demonstrating that the reference board does what it claims it can do.  We
could have a clause in there stating that the Bluetooth code is using bluez
and is only there to demonstrate that the Bluetooth part is working.  In
that case, the end customer may or may not want GPL so they may engage with
other such as StoneStreet (I know one customer who wants to use this board
that is likely to do that) or they may like be fine with the GPL and simply
use bluez.

I am new to the whole GPL/OSS thing; I've been buried under BSD stuff for
years and just starting in the Linux world.

Regards,


Pat Laplante
Principal Engineer
Vanteon Corporation
2851 Clover Street
Pittsford, NY 14534-1711
Office: (585) 248-0510 x298
Fax: (585) 248-0537
www.vanteon.com - Embedded for Your Future 

-----Original Message-----
From: bluez-users-admin@lists.sourceforge.net
[mailto:bluez-users-admin@lists.sourceforge.net] On Behalf Of Alec Myers
Sent: Saturday, March 25, 2006 6:30 PM
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Question about licensing!

Just to be quite clear: is your customer planning on selling the complete 
solution to the public? Or is it just an in-house project?

----- Original Message ----- 
From: "Patrick Laplante" <plaplante@vanteon.com>
To: <bluez-users@lists.sourceforge.net>
Sent: Saturday, March 25, 2006 10:13 PM
Subject: [Bluez-users] Question about licensing!


Hi all,



I am currently working on a Linux based project that need Bluetooth support.
I need to basically receive images from Bluetooth devices and print them.



The code printing the images is proprietary and can't be GPL'd.



Since bluez is GPL, I can't just link against it without being forced to
make my code GPL which I can't, my customer won't allow me to release their
IP to the public.



I was thinking of doing this:



A small daemon that uses the bluez library that would, on image reception
from a device, push the image to another print daemon over a name pipe or
socket.  Does this break the GPL in any way?  If I understand the license
correctly, I would have to make my Bluetooth daemon GPL but my print daemon
wouldn't have to be GPL.



Can you please confirm?  Do you guys have any issue with that?



The last thing I want to do is upset anybody or put my customer in a
position where he could be sued.  Worst case, I'll have to buy a stack from
a company like StoneStreet or implement a custom stack for my customer
(which will bump the price by a lot :-)).



Regards,



Pat Laplante
Principal Engineer

Vanteon Corporation
2851 Clover Street
Pittsford, NY 14534-1711
Office: (585) 248-0510 x298
Fax: (585) 248-0537
www.vanteon.com  <http://www.vanteon.com> - Embedded for Your Future







-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2006-03-25 23:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-25 22:13 [Bluez-users] Question about licensing! Patrick Laplante
2006-03-25 23:29 ` Alec Myers
2006-03-25 23:55   ` Patrick Laplante [this message]

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=E1FNIbj-0004oU-50@mail.sourceforge.net \
    --to=plaplante@vanteon.com \
    --cc=bluez-users@lists.sourceforge.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).