# Breakout Sessions
*For coordination, please contact Martine (@miri64) \<m.lenders@fu-berlin.de>*
![Breakout session schedule](https://page.mi.fu-berlin.de/mlenders/breakout-sessions-2021.png)
## CoAP API (re-)design
**Room:** [Room C](/xLUS4DyjQD-xof0s8A-WzQ?view)
**Time:** 7:30 - 8:00 (UTC+0)
**Contact:** chrysn (chrysn@fsfe.org), Martine (m.lenders@fu-berlin.de)
**Description:** Gcoap and nanocoap not only exist in parallel, they also share data structures like the pdu_t or the handler. Changes to Gcoap have accumulated Gcoap-specific fields in the pdu_t, but also make it hard to use Gcoap where even larger changes would be needed (handlers being told which transport data arrived from), and to utilize the underlying socket API to its full extent (thoughts of zero-copy access to data). Is the current level of entangelment sustainable? If not, how can we migrate? What's the fall-out? And once we've done that, can we just swap around CoAP transports and implementations like we swap network stacks? Is composability a topic to include (block-wise in userspace)?
**Structure and notes**: https://hackmd.io/o_y0nKfGRSqrkg-YTCf97g
## Kconfig migration
**Room:** [Room D](/xLUS4DyjQD-xof0s8A-WzQ?view)
**Time:** 7:30 - 8:00 (UTC+0)
**Contact:** Leandro Lanzieri (leandro.lanzieri@haw-hamburg.de), José Álamos (jose.alamos@haw-hamburg.de)
**Description:** An update on the status of the migration will be given, we will discuss particular modelling decisions that came up in PRs during the migration process and next steps.
**Notes Pad***: https://hackmd.io/kdS1QR2_TrC_KjblVKIP_g
## RIOTCtrl
**Room:** [Room C](/xLUS4DyjQD-xof0s8A-WzQ?view)
**Time:** 8:00 - 9:00 (UTC+0)
**Contact:** Francisco (francois-xavier.molina@inria.fr) and Martine (m.lenders@fu-berlin.de)
**Description:** General overview over new test infrastructure, [`riotctrl`](https://github.com/RIOT-OS/riotctrl), how it is used in the release tests, and demo how to use it in your tests.
**Presentation Pad**: https://notes.inria.fr/16Dz2mJTQySJsp-C83tmwg?view
## RUST
**Room:** [Room D](/xLUS4DyjQD-xof0s8A-WzQ?view)
**Time:** 8:00 - 9:00 (UTC+0)
**Contact:** Michael (mcr@sandelman.ca)
**Description:** discussion about how to best include RUST code into the current and planned(?) RIOT-OS build system
**notes pad** https://hackmd.io/XoCSxtOFQQGep-ol2NJD7Q?view
## Improved self-organization / Maintaining a Roadmap
**Room:** [Room C](/xLUS4DyjQD-xof0s8A-WzQ?view)
**Time:** 9:00 - 10:00 (UTC+0)
**Contact:** Kaspar (kaspar@schleiser.de)
**Description:** Continuation / recap on last year's "how do we improve community coordination"
**notes pad** https://notes.inria.fr/2uqycF2wSjqM4xjAAcLbvg#
At last year's Summit, we discussed procedures, RDMs, Task Forces and our coordination in general. Some of us where not happy back then.
Let's recap with one added year of experiences.
Current (outdated) roadmap: https://github.com/RIOT-OS/RIOT/wiki/Roadmap
-> following this year's [Open Assembly](https://forum.riot-os.org/t/riot-summit-2021-virtual-open-assembly/3353/4), let's try to sketch out how we could formalize subsystem maintainers
## C-Shanty sing-along
**Room:** [The Bar](/xLUS4DyjQD-xof0s8A-WzQ?view)
**Time:** Evening
**Contact:** <Please add!>
*I've decided to stop "programming in C" and to start "writing C shanties".*
{"metaMigratedAt":"2023-06-16T08:35:40.182Z","metaMigratedFrom":"YAML","title":"Breakout Sessions","breaks":"true","contributors":"[{\"id\":\"958684ea-d8f1-4188-8604-a34264b006d8\",\"add\":122,\"del\":0},{\"id\":\"0ded3a8a-00f6-4140-89f0-0f18fa004fdf\",\"add\":57,\"del\":0},{\"id\":\"0151a7f7-2b29-435c-8236-4fb44120e3a5\",\"add\":3619,\"del\":2684},{\"id\":null,\"add\":1593,\"del\":226},{\"id\":\"d9a39188-8c26-4db2-ad10-1d3baf13969b\",\"add\":583,\"del\":99},{\"id\":\"4a906b41-6f8f-48ef-8454-9d6aadfab718\",\"add\":351,\"del\":0},{\"id\":\"e41e3c19-ec3a-4ec0-89fb-3b71fe4e183d\",\"add\":42,\"del\":0}]"}