VMA 2020 09 RIOT Summit Minutes
Date: Sept 14th, 10:00 (CEST, UTC +2)
Moderator: Emmanuel
Attendees:
- Benjamin
- Bas
- Cenk
- Christian
- Hauke
- Hendrik
- Jean-Joseph
- Koen
- Michael Richardson (mcr)
- José
- Leandro
- Kevin
- Michel
- Matthias
- Thomas
- Francisco
- Marian (@maribu)
- PeterKietzmann
- Oleg
- Dylan
- Engin Koca
- Jiawei Lu
- Johan
- Julian Holzwarth
- Kaspar
- Martine
- Vincent
- Alex
- Emmanuel (@emmanuelsearch)
- Ines
- Timothy Claeys
-
Debrief 2020.07 release - 2min Moderator: Martine
-
A quick word from 2020.10 release manager - 2min Moderator: Koen
-
Determining the Release Manager 2021.01 - 5min Moderator: Emmanuel
-
Organization and moderation of the next VMA - 2min Moderator: Emmanuel
-
Review/Discuss preliminary list of break-out sessions Moderator: Oleg (2min) see https://pad.inria.fr/p/np_TZ8egxbg2bpbHClM
- Sprint day report. Moderation: Kaspar (10min)
- Fuzzing progress. Moderation: Koen (10min)
- Stance on "difficult" lingo (whitelist/blacklist...) Moderation: Kaspar (5min)
- Kconfig progress. Moderation: Leandro (10min)
- Coordinating RIOT development while keeping its GrassRoots Spirit. Moderation: Francisco (10min) https://pad.inria.fr/p/np_ryHIWrnjtua1sBy2
- Lots of test enhancements
- Most tests automated, run within 2 hours (github action)
- much easier than before. Press a button and the release is tested ;)
- 2020.07.1 released on Aug 28, 2020
- You can enter a RIOT version and run tests from here: https://github.com/RIOT-OS/RIOT/actions?query=workflow%3Arelease-tests Caveat: uses 2hours of the IoT-lab testbed, so not doable as is on a per PR basis But if you have the boards you can run locally!
- Koen sent dates already. Soft freeze is next week already.
- silence...
- someone at HAW default choice (roundrobin): José?
- Other candidates are welcome! PM Emmanuel if considering ;)
- Kevin volunteers!
see https://pad.inria.fr/p/np_TZ8egxbg2bpbHClM
- 5 sessions proposed
- Leandro: Updates and tech. insights about Kconf feature modeling
- Koen: "do we want to manage the stackoverflow tag" <- how do we want to manage it?
- José: breakout is more about "lower layers" not just MAC layer
- Bart Moons: break-out session details will follow Bart's presentation in the IoT Networking Session
- Kevin & Martine: Summary and Discussion of HiL / RIOTCtrl / Testing in general
- Kaspar: moved discussion of "difficult" words to VMA and/or? mailing list
** what are the numbers? 300Mb of pull requests! Not analyzed yet => below is Kaspar's impression ;) ** Sprint-Day started weekly, since the end of January, every Tuesday. Starts with a short synch videoconference meeting, ends with debrief. ** Kaspar's impression: format works in that it really quickens the process of reviewing/merging workflow for the PRs you care about ;) ** Sprinters: participants crosses "office boundaries". Inria, FU, HAW, Ben, Marian and others (please do add your name here ;)) ** Main take
Moderation: Koen Last Summit conclusions inculded: we must start with fuzzing our network stack
- GNRC TCP and CoAP can be tested by now
- Plan: integrate into nightlies tests
- Kaspar: maybe create easy way to "run it for an hour"
- Martine proposes fuzz topic for testing breakout session
- master/slave
- whitelist/blacklist
- whitespace?
- ...?
Kaspar: as a community we need to take position, cannot ignore this aspect. Aim to get the ball rolling until the next VMA?
- Michael: IETF is in the middle of this process
- Example: whitelist/blacklist is easily replaceable (accept list / block list). Whitespace is probably not replaced
- Matthias: +1. He got contacted by Akshay already regarding that topic.
- Leandro: Linux coding guid might have a section about alternative terminology
- Chrysn: do we have an actual list of terms that are considered problematic?
- Kaspar: Open a wiki / pad to collect ideas?
References on how others did: - Google Go: https://go-review.googlesource.com/c/go/+/236857/ - blacklist/whitelist => blocklist/allowlist - master/slave: context dependent (e.g., in unix pty, master / slave pty => control / process pty) - blackmagic probe: not renaming project (https://github.com/blacksphere/blackmagic/issues/680)
- tracking issue https://github.com/RIOT-OS/RIOT/issues/12888
- currently have ~60 modules, drivers, pkgs and net modules from sys
- quite some work, so help is welcome ;)
- starting phase 2 of migration: model in Kconfig symbols, default configurations for boards, CPUs, applications
- last part of migration would be convert all the makefiles
- related work: change the CPU arch symbols are used, modify hierarchy of CPU, architecture, boards.... Incremental builds when using Kconfig
Moderation: Francisco (10min) (wasn't 10 min...) https://pad.inria.fr/p/np_ryHIWrnjtua1sBy2
- Better way to organize work, which direkction to go, which topics to prioritize
- Other tools for communication?
** Users/Industrials needs *** Ben: one blocker/Issue is traffic not being encrypted (at MAC layer). Could be solved with the new HAL
** Technical Coordination Groups (sub-area maintainers) *** Kevin: we already have it with the task forces. One problem is maybe promoting them? Having deliverables? *** Emmanuel: is the problem "promoting" or "empowering"? *** Matthias: is it a matter of priorities? You choose you own priorities. We have RDMs to synch *** Emmanuel: we have tools and processes, but coordiation is not improving (e.g. RDMs have not demonstrated helping so much so far...)
** Visualizing whats missing, needed in RIOT *** Ben: Collect issues, bullet points of things that are missing in RIOT
*** MCR: you need Agile. If RDMs is done in 1 month good. Else you need some complentary organization. *** someone: need for some working-groups à la IETF?
Raise of hands: People agree that we have a coordination "issue"
Emmanuel: but are we even trying to improve? Martine: we had H&A but it is phasing out it seems... Kaspar: Sprint days are another example at small scale of trying to get better. But no real long term strategy coordination. No functional arena for that currently...
Kaspar: one example is Gunar PRs, which are not merge since a long time now limbo. Because there are trade-offs to be made, and there is no functional arena to decide on these (=> limbo is too often the result)
Oleg; priority question?
Michael Richardson: we are missing a list of outstanding issues Kaspar: get a worfklow for long stading changes., in a way to gather support
Emmanuel: we are running in circles around the question of "how do we use better subgroups dynamics" Emmanuel: do we have a proposal on the table on how to have working groups? Michael: working groups are maybe overkill. Monthly meetings are probably sufficient? https://github.com/dhood/pullrequest-visualiser http://www.sandelman.ca/tmp/riot-os-open-prs.png
Michael: maybe of interest? https://github.com/dhood/pullrequest-visualiser
Francisco: let's continue the discussion on the mailing list and during the Summit (=> side-meetings and breakout session on community processes)