BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.devconf.info//devconf-cz-2026//talk//8VK7CX
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-devconf-cz-2026-8VK7CX@pretalx.devconf.info
DTSTART;TZID=CET:20260619T101500
DTEND;TZID=CET:20260619T103000
DESCRIPTION:NetworkManager was designed twenty years ago to switch between 
 Wi-Fi and Ethernet on a laptop. Today it manages bonded interfaces\, hundr
 eds of VLANs\, and container host networking across millions of machines\,
  but the original architecture was never meant for this. A monolithic C da
 emon applying changes without transaction boundaries. The result: race con
 ditions at boot\, no reliable way to roll back a bad config\, and a host-c
 entric design never meant for containerized operation.\n\nNM-next is a gro
 und-up replacement\, written in Rust\, with one core architectural bet: a 
 transactional state engine that powers two execution modes. A one-shot mod
 e that applies config and exits with no daemon\, no D-Bus\, ideal for stat
 ic servers and container hosts. And a daemon mode for environments that ne
 ed continuous reconciliation. Same YAML\, same rollback semantics\, radica
 lly different deployment stories.\n\nIn 15 minutes\, we'll show you how we
 're rebuilding Linux network management from the ground up.
DTSTAMP:20260430T125306Z
LOCATION:A113 (capacity 64)
SUMMARY:NetworkManager was built for laptops - Here's what replaces it - St
 anislas Faye
URL:https://pretalx.devconf.info/devconf-cz-2026/talk/8VK7CX/
END:VEVENT
END:VCALENDAR