From: Stephen Crane <steve.crane@rococosoft.com>
To: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
Cc: halam.rose@7layers-uk.com,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Bluetooth Qualification - plan to make a plan
Date: 05 Mar 2003 12:47:25 +0000 [thread overview]
Message-ID: <1046868444.2860.1095.camel@baroque.rococosoft.com> (raw)
In-Reply-To: <1046865863.1823.55.camel@pegasus.local>
On Wed, 2003-03-05 at 12:04, Marcel Holtmann wrote:
> > BlueZ seems to be the sole copyright of Qualcomm - is this correct?
> >
> > Would it be appropriate to make the listing in the name of Qualcomm with Max
> > as the contact, or is there now some other kind of BlueZ organisation?
>
> The copyright thing is not very easy. The core code (HCI and L2CAP) are
> copyright of Qualcomm, the BNEP code contains copyright from Inventel
> and Max, the RFCOMM code has copyright from Max and me. The HCI drivers
> have much more different copyrights inside. For the user space part you
> will also get some more names.
>
> Maybe my idea with an own organization for BlueZ is a good one.
Or turn the copyright over to the FSF? (I'd push to have the user-space
libs relicensed under the LGPL first though.)
Later,
Steve
--
Stephen Crane, Rococo Software Ltd. http://www.rococosoft.com
steve.crane@rococosoft.com +353-1-6601315 (ext 209)
next prev parent reply other threads:[~2003-03-05 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 17:24 [Bluez-devel] Bluetooth Qualification - plan to make a plan Halam Rose
2003-03-05 12:04 ` Marcel Holtmann
2003-03-05 12:47 ` Stephen Crane [this message]
2003-03-06 22:51 ` Max Krasnyansky
2003-03-06 22:47 ` Max Krasnyansky
2003-03-07 13:49 ` [Bluez-devel] Qualification - name of owner and other admin Halam Rose
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=1046868444.2860.1095.camel@baroque.rococosoft.com \
--to=steve.crane@rococosoft.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=halam.rose@7layers-uk.com \
--cc=marcel@rvs.uni-bielefeld.de \
/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