Weekly coordination meeting

Community
,
21

Hej everyone!

2025-11-21T14: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

22

RIOT weekly coordination 21.11.2025, at 15:00 CET

Link: Jitsi Meet

Attendees

  • mikolai
  • benpicco
  • karl

Notes

release

23

RIOT weekly coordination 28.11.2025, at 15:00 CET

Link: Jitsi Meet

Attendees

  • Martine
  • Carl
  • Mikolai
  • Ann
  • Teufelchen

Note-takers

  • Moderation:
  • Notes:

Agenda

  • (crasbe) Push the usage of git-cache (esp. git-cache-rs)?
  • (Ann) PR Previews are really annoying

Notes

PR Previews are really annoying

  • Github intentionally disables write acces for forks
    • Goes against the PR flow we have for RIOT, breaks nearly every way to have PR previews using Github Pages
      • Alternative would have some security implications, due to write access
    • Murdock extremely confusing even if best target to add this
    • Since the site uses absolute links, it needs to set the base path on build, no clue how that gets generated in Murdock
    • My suggestion: Just ignore previews for now, building locally works fine enough

Push the usage of git-cache (esp. git-cache-rs)?

  • Crasbe not attending, pushed to next week

AOB

24

Hello everybody!

2025-12-05T14:00:00Z we will have our next weekly coordination meeting (sorry for the short notice).

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

25

RIOT weekly coordination 05.12.2025, at 15:00 CET

Link: Jitsi Meet

Attendees

  • Leandro
  • Teufelchen
  • Mikolai
  • Ann
  • Martine
  • Karl
  • benpicco

Note-takers

  • Moderation: Mikolai
  • Notes: Mikolai

Agenda

  • (crasbe) Push the usage of git-cache (esp. git-cache-rs)?
  • (ann) Can we remove the “(Deprecated)” sites on doc.riot-os-org already?
  • (martine) Release schedule / VMA planning?

Notes

Push the usage of git-cache (esp. git-cache-rs)?

  • crasbe (offline): many microcontroller platforms download CMSIS, nrfx, … which takes a lot of time and bandwidth
  • git-cache exists, but does not support sparse checkouts (which for example would download the full nrfx instead of just the headers)
  • git-cache-rs only used if explicitly in ENV
  • Print info message about git-cache-rs when not using that?
  • Deprecate support for git-cache?
  • Ann: just say yes?
  • Martine: I’d say yes, but only if feature-complete
  • Mikolai: @crasbe: can you confirm?

Can we remove the “(Deprecated)” sites on doc.riot-os-org already?

  • Ann: They are ugly, provide nearly no value, and make it feel like RIOT is completely out of support / unmaintained
  • Ann: Also sidebar looks really overwhelming when in reality 95% of it is just links to the guide site
  • Ann: Besides that, I’d argue applying a deprecation strategy meant for actually used functionality to simple guide articles is superfluous
  • Ann: It has been half a year since the first deprecations, it just looks silly
  • benpicco: deprecation process is only for API
  • Martine: deprecation was meant for period where guides site was not ready yet, if thats not the case
  • Mikolai: redirects were tricky right?
  • Martine: we could do server-redirects?
  • Ann: might be tedious?
  • Martine: we can just redirect all html files from doxygen, will do it
  • Leandro: guides should be more prominent on doxygen (people agreeing)
  • Ann: propose to almost entirely remove main page, point to guide site, just say “this is API documentation” (people agreeing), will do
  • Martine: put a note about redirects somewhere in doxygen, so if names are reused in Doxygen, we are not confused years from now
  • Karl: maybe just use HTML redirects so it works locally?
  • Martine: would rather use Caddy, less troublesome
  • Mikolai: and redirects on local deployments are less of a concern

Release schedule / VMA planning?

  • benpicco: release ready any moment, waiting for release-note PRs to pass CI
  • Martine: push VMA to January? clash with 2026.01 release?
  • Leandro: tentative plan for release by end of January
  • Martine: would try beginning of January, will start poll also including next week
26

Hello everybody!

2025-12-12T14: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

27

RIOT weekly coordination 12.12.2025, at 15:00 CET

Link: Jitsi Meet

Attendees

  • Martine
  • maribu
  • Karl
  • Elena
  • mikolai

Note-takers

  • Moderation: Martine
  • Notes: Mikolai

Agenda

  • ccache performance issues
  • VMA 2025.11

Notes

ccache performance issues

  • maribu: have downstream performance problem
  • maribu: cache can not be used as soon as CFLAGS (riotbuild.h) change, even if some part is not affected
  • maribu: riotbuild.h is added to every C file with -I
  • maribu: proposal: split into cpubuild.h, boardbuild.h, etc., and let C files explicitly include those
  • Karl: global variables instead of defines?
  • Martine: maybe previous kconfig work could help as variables are already split into modules
  • maribu: would be breaking API change, new include(s) needed for downstream users (could update in-tree)
  • maribu: clarify: only take out variables that hit ccache hard (BOARD, CPU, etc), also modules used?
  • Martine: but those would be a loooot of users in-tree, really huge work, not sure if that’s time well spent
  • Mikolai: important to make sure compilation that uses #if MODULE_* would break loudly, and not just silently assume modules are not there
  • maribu: could do refactor iteratively, leave out modules for now. but then ccache improvements only if modules are exactly the same between two configurations. at least improvement for CPU/BOARD, all applications will hit ccache if build for different CPU/BOARD
  • Martine: concerned about time investment in fixing compared to time savings in CI
  • maribu: really pressing for MLPA, 1 weekend vs. 2h/week per coworker in coming year
  • Martine: agree for CPU/BOARD, but concerned about MODULES
  • maribu: sounds like consensus: all but modules, then discuss whether tackling that, too
  • (agreement in the room)
  • Martine: wasn’t there another central include header generated by Kconfig?
  • maribu: probably less impact in Murdock as in downstream CI since Murdock workers run 24/7 and ccache is hot after ~1 week

VMA 2025.11

  • Martine: probably 9.1., even if kind of late

AOB

  • Martine and Mikolai on vacation next week, if you want to meet, please organize yourself
28

FYI: We will skip this week’s meeting once more as it conflicts with the 2025.11 VMA. As always, we will publish the notes of that meeting afterwards under the vma tag.

29

Hello everybody!

2026-01-16T14: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

30

RIOT weekly coordination 16.01.2026, at 15:00 CET

Link: Jitsi Meet

Attendees

  • Martine
  • Leandro
  • Ann
  • Karl
  • Teufelchen
  • Stepan
  • Leonard Herbst
  • Elena
  • Mikolai

Note-takers

  • Moderation: Martine
  • Notes: Mikolai

Agenda

  • Future of RIOT on Github
  • LLM and Plagiarism Policy
  • Handling updates that affect Rust projects

Notes

Future of RIOT on Github

  • Ann: really easy to mirror Codeberg
  • Ann: I don’t see a reason against it
  • Martine: Me neither. Just question of RIOT-OS vs. RIOT in org name
  • Martine: are org redirects / aliases possible?
  • Ann: will check, probably not
  • Mikolai: mirroring just code or also issues/PRs?
  • Martine: I was talking just about code
  • Ann: there are bots that could do issues, but not sure if we are ready for this
  • Martine: migrating to codeberg is a potential future step, involves rewriting CI etc.
  • Ann: Codeberg does have fairly competitive CI, but no mergequeue there
  • Ann: open question: one-time copy issues / PRs?
  • Mikolai: now or later? advantage if stale copy at later point?
  • Ann: only preservation
  • Martine: would be topic for later
  • Karl: implication for self-hosted CI costs on Github on RIOT?
  • Ann: announcement got reverted
  • Martine: maybe just applied to custom workers, iirc we don’t have that anymore
  • Karl: so wouldn’t have hit us anyways
  • Martine: consensus: will mirror to codeberg on one of the two org names, decide on org name later

LLM and Plagiarism Policy

  • Martine: background: obvious plagiarism by new contributor, reusing code but changing attribution
  • Martine: Adjacent topic: LLM-generated contributions. How to handle? Wikipedia talk gives summary on why LLMs are used: AI-generated content in Wikipedia - a tale of caution - media.ccc.de
  • Karl: how could LLM users even ensure that copyright is not violated?
  • Martine: ideally, they shouldn’t use LLMs, but if they do, they have to declare it explicitly
  • Karl: original author couldn’t be found. So how would we handle it when we get such a PR?
  • Martine: at least they have to provide the prompt
  • Stepan: LLMs also hallucinate about sources
  • Karl: if a complete module would be LLM-generated, we would need to decline it, right?
  • Martine: yes
  • Karl: what about LLM-assisted then?
  • Martine: similar to Kaspar’s example of local llama instance for code snippets
  • Karl: locality shouldn’t be a decisive factor
  • Mikolai: summarizing: LLM-generated + plagiarism delcined, LLM-assisted okay iff declare
  • Ann: why would people declare if not noticeable?
  • Mikolai: because it is in our contribution guidelines, we cannot do more
  • Martine: wanted to have it written down so we can point to it in such cases
  • Elena: VSCode has integrated Copilot nowadays, people use it a lot, so would everyone declare it?
  • Mikolai: I would say yes
  • Ann: Could just be a checkbox
  • Elena: how useful is this information for reviewers? just to be more careful while reviewing?
  • nodding
  • Elena: are LLMs really plagiarism if they just mix-and-match?
  • Martine: even snippets can be attributed
  • Ann: RIOT usecase is quite niche, so LLMs do copy entire files verbatimely
  • Elena: would be harsh, but not too harsh, remembering that a lot of students using RIOT use LLMs already
  • Martine: Yes, but having this in the Contribution guidelines would help students to learn that this is not okay
  • Martine: we agree that we want such an amendment, details can be discussed in PR. Who volunteers?
  • Karl: I’ll try

Handling updates that affect Rust projects

AOB

Guides are the new docs

  • Martine: guides content deployed on tattoine
  • Martine: also, redirects for doc./*.html → api./*.html are in place
  • Martine: we just need to wait for Oleg to update the CNAME for guide. and guides., then we can reconfigure doc./docs.

Kconfig PR

Release 2026.01

  • Leandro: hard feature freeze, automatic tests look good for now
31

Hello everybody!

2026-01-23T14: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

32

RIOT weekly coordination 23.01.2026, at 15:00 CET

Link: Jitsi Meet

Attendees

  • Stepan
  • Leandro
  • Mikolai
  • Ann
  • Karl
  • Martine :three_o_clock:

Note-takers

  • Moderation: Mikolai
  • Notes: Mikolai

Agenda

  • Guides are the new docs
  • Kconfig PR
  • Release 2026.01
  • Move first Repo to Codeberg
  • LLM PR

Notes

Guides are the new docs

  • Tom: everything works fine, not sure what to discuss, Oleg updated CNAME
  • Martine: last open action item gh-pages branch can now be deleted, after deployment action is cleaned up
  • Tom: will do

Kconfig PR

Release 2026.01

  • Leandro: hard feature freeze, automatic tests look good for now
  • Leandro: some issues with lvgl package, fixed, issue with ESP8266, Gunnar is checking
  • Leandro: RC2 with fixes, release might be delayed a bit

Move first Repo to Codeberg (:frog:)

  • After discussing it with Chrysn I’d like to move a Rust repo to be bi-directional (Accepting PRs/Issues on Codeberg as well) as the first test subject
  • Pull from Codeberg
  • Get people warm with important but not too important repo on Codeberg
  • Try out the flow to see whether this could work for RIOT/RIOT
  • Tom: mirroring was simple, next step would be two-way mirror, however such bot solution does not promising
  • Tom: suggestion by chrysn: track issues/PR both on codeberg and Github, first try out with rust-repos
  • Mikolai: what about CI there?
  • Tom: easy for those two, but would be much more complicated for RIOT main repos
  • Mikolai: good to try out with less impactful repos
  • Martine: link codeberg repo on website?
  • Tom: maybe defer after discussion in future VMA?
  • people agreeing

LLM PR

33

Hello everybody!

2026-02-06T14: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

34

RIOT weekly coordination 06.02.2026, at 15:00 CET

Link: Jitsi Meet

Attendees

  • maribu
  • mcr
  • karl
  • mikolai
  • martine

Note-takers

  • Moderation: Mikolai
  • Notes: Mikolai

Agenda

  • VMA Meeting Dates
  • picolibc/newlib as pkg?
  • static analysis PRs

Notes

VMA Meeting Dates

  • Martine: release maintainers not in the call, so no point in discussing further
  • so lets keep it tuesday

picolibc/newlib as pkg?

  • Mikolai: why do we use host-system-provided picolibc/newlib instead of as a pkg?
  • Martine: was probably before time of pkg? didn’t want to need toolchain installation by hand. now that we have it, would be nice to switch over.
  • maribu: would be nice, but very sceptical. knowledge from Alpine maintership of newlib/picolibc: interdependencies for c++/rust?
  • maribu: a lot of configurables (size of wchar), if doesn’t match libstd++, if you don’t care about c++, might be doable.
  • maribu: joakim has cmake-based RIOT build system, he had picolibc as pkg, no pointers left unfortunately
  • maribu: practical point for newlib: build system complete mess, will take forever; picolibc is much faster to compile
  • maribu: bottomline: picolibc will do if not caring for c++, for c++ it may work or not, for rust it should work
  • maribu: newlib should be considered obsolete
  • Martine: picolibc as default already?
  • maribu: no, issue was that distros didn’t package up-to-date versions
  • mikolai: so pkg-approach might be doable?
  • maribu: yes. but gotcha: for espressif, newlib stays attractive since they have binary-blob wifi + outdated newlib in masked ROM
  • karl: real advantage given huge flash space on esp?
  • maribu: yes, RAM savings (ESP* need to execute ISR code from masked ROM and IRAM to prevent random crashes on locked flash)
  • mikolai: leave newlib for ESP, use picolibc everywhere else?
  • maribu: yes, would work
  • karl: picolibc on native?
  • maribu: theoretically possible, but many months of engineering

static analysis PRs

AOB

  • mikolai: looks like CLT booth has been accepted (no official notification out yet)
35

Hello everybody!

2026-02-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

36

Hello everybody!

2026-02-20T14: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

37

RIOT weekly coordination 20.02.2026, at 15:00 CET

Link: Jitsi Meet

Attendees

  • Martine
  • Maribu
  • Karl
  • Mikolai

Note-takers

  • Moderation: Martine
  • Notes: Martine

Agenda

Notes

nanocoap API changes

  • Will provide a PR for bug report next week

Bug bounty requests on the security@riot-os.org

AOB

38

Hello everybody!

2026-02-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).

Best
Martine