From: Vinicius Gomes <vinicius.gomes@openbossa.org>
To: BlueZ <linux-bluetooth@vger.kernel.org>
Subject: BlueZ GSoC 2010
Date: Thu, 18 Mar 2010 22:50:46 -0300 [thread overview]
Message-ID: <2a9506371003181850h15a417a4u35bc0ed70e60f548@mail.gmail.com> (raw)
Hi,
BlueZ just got accepted as an organization for this year's Google
Summer of Code.
There is a small list of project ideas here[1], for the next days we
need to polish it and add more content. Any help is appreciated.
We are also looking for mentors, if this idea interests you, please
contact me off-list or go to #bluez-gsoc at freenode, this is also
where most of the discussion regarding GSoC will take place, in case
you just want to follow it.
As always, patches and suggestions are welcome ;-)
And thanks to everyone who contributed ideas to that list.
Cheers,
--
Vinicius Gomes
INdT - Instituto Nokia de Tecnologia
[1] http://hostisdown.org/gsoc/
next reply other threads:[~2010-03-19 1:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 1:50 Vinicius Gomes [this message]
2010-03-22 12:13 ` BlueZ GSoC 2010 Bastien Nocera
2010-03-22 16:14 ` Luiz Augusto von Dentz
2010-03-22 17:27 ` Bastien Nocera
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=2a9506371003181850h15a417a4u35bc0ed70e60f548@mail.gmail.com \
--to=vinicius.gomes@openbossa.org \
--cc=linux-bluetooth@vger.kernel.org \
/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).