Link ID: (required)
bluez
Group Name: (required)
BlueZ
Home Page URL: (required)
http://www.bluez.org/
Public Email: (required)
http://www.bluez.org/
Description: (required)
BlueZ provides support for the core Bluetooth layers and protocols.
It is flexible, efficient and uses a modular implementation.
It has many interesting features such as:
* Complete modular implementation
* Symmetric multi processing safe
* Multithreaded data processing
* Support for multiple Bluetooth devices
* Real hardware abstraction
* Standard socket interface to all layers
* Device and service level security support
Currently BlueZ consists of many separate modules:
* Bluetooth kernel subsystem core
* L2CAP and SCO audio kernel layers
* RFCOMM, BNEP, CMTP and HIDP kernel implementations
* HCI UART, USB, PCMCIA and virtual device drivers
* General Bluetooth and SDP libraries and daemons
* Configuration and testing utilities
* Protocol decoding and analysis tools
* Audio Service witch gives support to profiles:
HSP, HFP, AVDTP, A2DP, AVRCP
* Input Service profiles: HID
* Network Service profiles: PAN
* Serial Service profiles: RFCOMM
Why is your group applying to participate? What do you hope to gain by participating? (required)
With the growing number of the devices witch uses BlueZ as the Bluetooth
stack it would be good to students to learn about it and for us to
gain more contributors making the Bluetooth experience in Linux even
better.
What is the main public mailing list for your group? (required)
linux-bluetooth [at] vger.kernel.org
Where is the main IRC channel for your group? (required)
#bluez (and #bluez-users for non-development) @ irc.freenode.net
What criteria do you use to select the members of your group? Please be as specific as possible. (required)
We try to select accessible active developers who are willing to spend some time guiding the students through
the code and reviewing the what was produced.
Has your group participated previously? If so, please summarize your involvement and any past successes and failures.
Yes, we participated last year. Even for our first involvement with Google Summer of Code, it was a great experience,
even with one disappearing student. But we got to know some very good people that are still helping us and some
friend projects a lot.
If your group has not previously participated, have you applied in the past? If so, for what sort of participation?
What license does your organization use? (required)
GNU General Public License (GPL) and GNU Lesser General Public License (LGPL)
What is the URL to the ideas list of your organization? (required)
http://wiki.bluez.org/wiki/GSoC2009
What is the main development mailing list for your group? (required)
linux-bluetooth <at> vger.kernel.org
What is the application template you would like contributors to your organization to use (required)
What is your plan for dealing with disappearing contributors? (required)
At first we would like to keep them interested enough so they don't disappear ;) .
If that doesn't happen for whatever reason, the plan is to find out that the contributor
is not insterested as soon as possible and work it out, either by making some adjustments
to the project scope or releaving this contributor.
What is your plan for dealing with disappearing members? (required)
For disapearing members the plan is to have backup people with enough knowledge about
the project, who could take over this project.
What steps will you take to encourage contributors to interact with your community before, during, and after the program? (required)
The BlueZ community is very active, developers are always available in
irc channel and mail list, so we will try to make students to became
part of it, chatting with the developers in #bluez or mailing them in
the mail list.
Showing to them how Bluetooth and Linux technologies are fun to work with. And how much work and learning are still
left to be done.
Please select your backup group administrator.
vcgomes
