Weekly coordination meeting

Community
,
41

Hello everybody!

2026-03-13T14:00:00Z we will have our next weekly coordination meeting.

The meeting will take place online on Jitsi.

Please add your agenda items to our pad for the meeting minutes, so we know beforehand if there is anything to discuss (some people decide their attendance on that).

Best
Martine

42

Hello everybody!

2026-03-27T14:00:00Z we will have our next weekly coordination meeting.

The meeting will take place online on Jitsi.

Please add your agenda items to our pad for the meeting minutes, so we know beforehand if there is anything to discuss (some people decide their attendance on that).

Most of the people from TU Dresden and HAW Hamburg will be not be able to join, but please, feel free to organize among you.

Best
Martine

43

Hello everybody!

2026-04-10T13:00:00Z we will have our next weekly coordination meeting.

The meeting will take place online on Jitsi.

Please add your agenda items to our pad for the meeting minutes, so we know beforehand if there is anything to discuss (some people decide their attendance on that).

Best Mikolai

44

RIOT weekly coordination 10.04.2026, at 15:00 CET

Link: Jitsi Meet

Attendees

  • crasbe
  • carl
  • mikolai
  • karl

Note-takers

  • Moderation: Mikolai
  • Notes: Mikolai

meeting

Agenda

  • MCR asks: recent addition discussion about new maintainer (EF)… did something go wrong here?
  • CS asks: static const in headers
  • CS asks: SPI API

Notes

static const in headers

  • Carl: seems like black magic, just used to be optimized out
  • Karl: just works because never actually put in binary
  • Carl: is this a coding convention? are we sure optimizing out always works
  • crasbe: can we just try if linker is smart enough
  • Karl: compiler works per definition, linker might depend on implementation
  • mikolai: first step: document why we are using static const in headers

SPI API

  • Carl: API broken: meaning of SPI_DEV(x) not defined in documentation, physical peripherals not always defined as available, why are pins combined with peripherals
  • Karl: same with UART and I2C
  • carl: why?
  • karl: portability to other boards, I2C “just works”
  • crasbe: peripheral instances might differ quite a lot, different configuration etc, pins as defined on board
  • carl: concrete board: adafruit-feather-nrf52840-sense, why second SPI?
  • crasbe: second for flash. speciality for nrf52: you can freely configure pins for peripherals
  • Karl: most boards / MCUs have hard-wired peripherals anyways
  • carl: so again, missing documentation
  • carl: but still, not very beginner-friendly to need to change random headers
  • (some discussion about more user-friendly macro interface, but concerns about compiler optimizations)
  • crasbe: created a PR to improve documentation: drivers/periph/spi: add doc about multiple SPI buses by crasbe · Pull Request #22185 · RIOT-OS/RIOT · GitHub