All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Qualified :)
Date: Thu, 14 Apr 2005 18:32:22 +0200	[thread overview]
Message-ID: <1113496342.8989.50.camel@pegasus> (raw)
In-Reply-To: <Pine.LNX.4.33.0504141803530.29800-100000@redbean.intranet.gw-instruments.de>

Hi Peter,

> hhmmm. First it is nice to here that BlueZ is qualified (even if this does
> not mean that it doesn't have bugs ;-). The question is if and how this
> qualification can be used for other qualifications as a pre-qualified
> component ??

trust me there are still bugs, but even the test system has bugs ;)

It is possible to use the BlueZ listing. Look at the Tom Tom GO300 for
an example.

> On one hand BlueZ itself is GPL software, and as such can be used by
> anybody as long as the GPL is respected. On the other hand the
> qualification and listing has been payed by a company and I was wondering
> if they could have any control if some other company references their
> listing in their own product listing. Or are they just generous and don't
> care ??

Tom Tom has no copyright on the BlueZ core code. Nothing has changed
with this listing. As far as I know you can always refer to other
listings and so Tom Tom can't control it. However the only reason that
it is not listed under my name is, that the Bluetooth SIG don't allows
qualifications by individual users. Only companies can qualify products.
A stupid thing from my point of view.

The only option that I see to get this really clean is to create a
non-profit organization that takes care of such things. However I don't
really have time for this paperwork, but if someone wants to go this
way, I am in.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-04-14 16:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-14 15:52 [Bluez-devel] Qualified :) Dimitry Andric
2005-04-14 16:13 ` Peter Wippich
2005-04-14 16:32   ` Marcel Holtmann [this message]
2005-04-14 15:46     ` James Courtier-Dutton
2005-04-14 16:57       ` Marcel Holtmann
2005-04-14 16:23 ` Marcel Holtmann

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=1113496342.8989.50.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@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 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.