public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "KeiHachi" <keihachi@swissinfo.org>
To: <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Questions about BlueZ in  commercial use
Date: Sun, 27 Jun 2004 18:47:06 +0900	[thread overview]
Message-ID: <003401c45c2b$b6eab240$0364a8c0@haruo> (raw)

Hi.

I have some questions about BlueZ.

Our company is investigating now about BlueZ,
to determine whether it is useful to use in our commercial product, or not.

I searched the archive of BlueZ mailing list about Q&A of BlueZ in commercial use.
I found some threads which are related to such a topic, but I want to know more detail.


Please reply on the following questions.

Q1. development schedule in the future
I saw  "http://www.bluez.org/todo.html"
But there is no information I want to know.
Please tell me the following things.

- eSCO (enhanced SCO) in Bluetooth 1.2
Do you have any plan to develop these?

- Audio/Video related profiles
Do you have any plan to develop these(A2DP, AVRCP)?


Q2. maintenance/support
I found some examples about the support of open-source that
companies which want to use such a open-source software,
pay some maintenance fee to the community or some companies which
provide the service to maintain it, so that
the community or such companies ensure the quality of their software is a certain level.
For example, MySQL, JBoss, etc.
These open-sources are maintained to ensure the quality,
by some kind of organizations which get the maintenance fee.

Does BlueZ allow such a business model?


Q3. version control
Many open-sources are composed of two versions,
one is a "testing version", and another is a "stable version". 
But I think BlueZ has only a "testing version".

Why doesn't BlueZ have a "stable version"?
Do you have any plan to have a "stable version" of BlueZ?


I will appreciate any reply.

Thanks.
Keihachi




-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2004-06-27  9:47 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-27  9:47 KeiHachi [this message]
2004-06-27 12:52 ` [Bluez-devel] Questions about BlueZ in commercial use Nicholas A. Preyss
2004-06-27 14:45   ` KeiHachi
2004-06-27 17:13     ` Nicholas A. Preyss
2004-06-28 16:30       ` KeiHachi
2004-06-28 17:22         ` Marcel Holtmann
2004-06-27 18:29     ` Marcel Holtmann
2004-06-28 16:33       ` KeiHachi
2004-06-28 17:45         ` Marcel Holtmann
2004-06-28 14:39   ` Ademar de Souza Reis Jr.
2004-06-28 14:48     ` Marcel Holtmann
2004-06-28 15:19       ` Ademar de Souza Reis Jr.
2004-06-28 15:38         ` Marcel Holtmann
2004-06-28 15:59           ` Stephen Crane
2004-06-28 17:06           ` Ademar de Souza Reis Jr.
2004-06-28 17:15             ` Marcel Holtmann
2004-06-27 18:09 ` Marcel Holtmann
2004-06-27 19:10   ` Nicholas A. Preyss
2004-06-27 19:09     ` Marcel Holtmann
2004-06-27 20:34       ` Nicholas A. Preyss
2004-06-27 20:49         ` Marcel Holtmann
2004-06-27 21:42           ` Nicholas A. Preyss
2004-06-28  7:37             ` Marcel Holtmann
2004-06-28 16:28   ` KeiHachi
2004-06-28 17:13     ` Marcel Holtmann
2004-06-29 17:08       ` KeiHachi
2004-06-29 17:41         ` Marcel Holtmann
2004-06-30 16:22           ` KeiHachi
2004-06-30 18:11             ` Marcel Holtmann
2004-07-04  8:57               ` KeiHachi
2004-07-04 11:38                 ` Marcel Holtmann
2004-07-04 13:19                   ` Peter Favrholdt
2004-07-04 13:47                     ` 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='003401c45c2b$b6eab240$0364a8c0@haruo' \
    --to=keihachi@swissinfo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox