From: George Kiagiadakis <george.kiagiadakis@collabora.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: BlueZ Face-to-Face Meetup - Nice, France, May 30-31, 2026
Date: Mon, 20 Apr 2026 17:44:18 +0300 [thread overview]
Message-ID: <3279c8579e9c1750c672bc070b91a48c13a3f4e7.camel@collabora.com> (raw)
In-Reply-To: <39DA4E65-9DE8-4857-8776-41F7BAF00C56@collabora.com>
On Wed, 2026-02-11 at 10:50 +0200, George Kiagiadakis wrote:
> Hello everyone,
>
> We are pleased to announce a BlueZ face-to-face meetup in Nice, France on May 30-31, 2026. The meetup is organized and sponsored by Collabora and will take place right after the Embedded Recipes [1] conference, co-located also with other events.
>
> This is an excellent opportunity for developers and stakeholders to meet in person, discuss current development priorities, and collaborate on technical challenges. You are very welcome to join us!
>
> Announcement: https://github.com/orgs/bluez/discussions/1881
> Dates: Saturday, May 30th & Sunday, May 31st, 2026
> Location: Radisson Blu Hotel Nice
>
> Registration is free of charge, but we kindly ask you to confirm your attendance by commenting on the GitHub discussion thread: https://github.com/orgs/bluez/discussions/1881#discussioncomment-15756005
>
> The meetup is strategically scheduled adjacent to several related events:
>
> - Embedded Recipes conference (May 27-28) [1]
> - PipeWire hackfest (May 29-30) [2]
> - Linux Media Summit, Buldroot hackathon, libcamera, Yocto Project and others... [3]
> - Bluetooth SIG Member Summit & UPF in Milan (June 2-7) - conveniently accessible via train from Nice
>
> Note that the meetup will share the venue with the PipeWire hackfest on Saturday. This co-location offers additional opportunity to nail down LE Audio integration topics that are shared between the two projects.
>
> We look forward to productive discussions and the opportunity to strengthen collaboration within the BlueZ community.
>
> Best regards,
> George
>
> [1]. https://embedded-recipes.org/2026/
> [2]. https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/PipeWire-Hackfest-in-Nice---May-2026
> [3]. https://embedded-recipes.org/2026/colo/
>
> --
> George Kiagiadakis
> Principal Software Engineer
>
> Collabora Limited | Unit 1.06, St John's Innovation Centre, Cowley Road, Cambridge, CB4 0WS, UK
> Registered in England and Wales | Company No. 05513718
>
>
Hello everyone,
This is a reminder for the upcoming f2f meetup in Nice, on May 30-31. The time
is approaching, so if you are planning to attend and haven’t yet booked, now is
a good time! Also please remember to register, so that we know how many people
to expect.
PS: there will be option to attend discussions remotely, if you are unable to
join us in person and you want to participate. But of course, face to face is a
different (and highly recommended) experience!
Best regards,
George
next prev parent reply other threads:[~2026-04-20 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 8:50 BlueZ Face-to-Face Meetup - Nice, France, May 30-31, 2026 George Kiagiadakis
2026-04-20 14:44 ` George Kiagiadakis [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-10 19:54 George Kiagiadakis
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=3279c8579e9c1750c672bc070b91a48c13a3f4e7.camel@collabora.com \
--to=george.kiagiadakis@collabora.com \
--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