Weekly coordination meeting

Community
,
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