Open kaspar030 opened 4 months ago
Addendum for Device Lifecycle:
On-boarding
When networking itself requires onboarding that has neither TOFU nor Zero-Touch capabilities, it'd be convenient to have a cheap extra on-boarding channel. This may be USB Ethernet, WebUSB or Bluetooth, which can set up WiFi credentials. Using that interface should ideally be accessible to users unfamiliar with programming, eg. by having configuration options exposed as MTP files, or even a web application that provides different levels of interface to an attached device's configuration (eg. key-value manipulation or forms for described fields).
(inspired by a fedi thread)
This is the Roadmap tracking issue, See below breakdown, more or less kept up-to-date. For now we are prioritizing features and issues relating to the 1st release milestone.
Development tools & Documentation
164
OS functionality
Embassy integration
driversinitialization -> covered through riot-rs-boards & autostart tasksHardware Support
RIOT-c support
(postponed)
Basic (Layer<5) networking support
Extended (Layer>4) networking + security
Device Livecycle
Extend embassy integration
Board support traitnot using a traitExtend hardware support
CI
Formal Verification