Martine: Idea to do it in Dresden next year. Madrid was floated (colocate with IETF). Emmanuel: Like colocation. That’s how we started initially with the Summit, and it did us real good. chrysn: Next opportunity would be Vienna 2026 emmanuel: Could ping Jaime about Madrid? Ericsson? Martine: colocate the IETF hackathon with the IETF Hackathon? chrysn: Could do an organized Friday hack-together. emmanuel: Also consider other useful overlaps, e.g. FrOSCon Martine: Hannes is now there.
it is quite important that we announce next year’s location during the closing of this year’s Summit, as we did before. this year it is even more important since we have larger number of registered participants outside of the usual RIOT crowd.
in Dresden, we have a setting that simply works, including a vibrant IoT, chip etc. community around. if anybody has another venue proposal for 2025 with strong commitment, it would be good to share.
regarding co-locating the Summit with another event such as IETF: this has advantages, and it is definitely worth thinking about. but it also adds additional challenges. based on my experiences organizing RIOT Summits it requires a bit more time in advance to confidently change the mode of operation. one crucial topic is the event date. co-locating with IETF 123 would move the Summit to July – changing the rhythm is possible but announcing it well in advance would be helpful.
On the one hand, I very much like the idea of co-locating the Summit with IETF
and we’ve been very German-speaking centric with the summits recently. On the
other hand, I don’t find Madrid in July very attractive and the truth is that
the RIOT community is still very German-centric so travel costs would
definitely increase for a bigger part of the community.
Cheers
Oleg
P.S. For those who haven’t realized: RIOT is quite prominent in the banner
picture for the IETF meetings page: IETF | Upcoming meetings
(very left part of the pic).
The notes makes the point seem larger than it actually was. I think the tentative conclusion at least during the meeting (which is missing from the notes) was: Go for Dresden next year, as it is somewhat 25th hour to change that decision anyways, but keep the idea of co-location for 2026 open (would be Vienna again, btw).
In 2022 I was able to make the Hamburg summit in person because I had longer travel plans in Germany. Ones that would have brought me closer, but they broke. I made the summit in 2019 in Helsinki via a combination of just lumping it, and the Linux Plumbers conference being “nearby” (Lisbon…)… Nearby being a relative term.
Had this year’s event been, say, Sept.16/17, (in Vienna!) I could have fit it in between DESCON, and LPC. That would have justified the CO2 for Atlantic-crossing for me. As is, I’m going to none of them.
I will get up early (3am) on Thursday and Friday for this year’s summit. It’s okay-ish that it’s remote, but naturally the hallway track is very important.
I understand that Madrid in July would be not be that pleasant, and it’s not that easy to get to by train. I would caution against Friday just before IETF hackathon, but Wednesday/Thursday might be okay.
What about Bilboa, ES? Or Bayonne, FR? {okay, I just want to go surfing}. No, I know no hosts in that part of the world
2025 is not a good year for co-location with IETF.
I have no problem with Dresden, it’s the question of timing.
RIPE91, 20-Oct-2025. Not a lot of cross-over I agree.
so, yes, please announce early. For timing, consider:
Hmm. That used to have dates on it. Where is the one I want?
Michael Richardson via RIOT notifications@riot-os.org wrote:
> I understand that Madrid in July would be not be that pleasant, and
> it’s not that easy to get to by train. I would caution against Friday
> just before IETF hackathon, but Wednesday/Thursday might be okay.
> What about Bilboa, ES? Or Bayonne, FR? {okay, I just want to go surfing}. No, I know no hosts in that part of the world
> 2025 is not a good year for co-location with IETF.
> I have no problem with Dresden, it's the question of timing.
> RIPE91, 20-Oct-2025. Not a lot of cross-over I agree.
Or, consider INRIA/Paris a few days after IETF123 (Madrid).
Not Saturday/Sunday, but maybe Tuesday/Wednesday.
I prefer not to do stuff before IETF (because I’ll get there exhausted, and
there are a 100 small things to get done), but I don’t mind after.
–
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
emmanuel: Could ping Jaime about Madrid? Ericsson? Martine: colocate the IETF hackathon with the IETF Hackathon? chrysn: Could do an organized Friday hack-together. emmanuel: Also consider other useful overlaps, e.g. FrOSCon Martine: Hannes is now there.