BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//devconf-cz-2024//talk//NMQDGE
BEGIN:VTIMEZONE
TZID:Europe/Prague
BEGIN:DAYLIGHT
DTSTART:20230616T000000
TZNAME:CEST
TZOFFSETFROM:+0200
TZOFFSETTO:+0200
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20231029T030000
RDATE:20241027T030000
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20240331T030000
RDATE:20250330T030000
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:What lies beyond the kernel's email workflow? - Nikolai Kondrashov
 \, Tales da Aparecida
DTSTART;TZID=Europe/Prague:20240615T123000
DTEND;TZID=Europe/Prague:20240615T130500
DTSTAMP:20260813T124347Z
UID:pretalx-devconf-cz-2024-NMQDGE@pretalx.com
DESCRIPTION:The email workflow brought the Linux kernel to life and saw it
  through immense growth and into widespread popularity. However\, it seems
  it's reaching its limits\, prompting Linus Torvalds to say we need to "fi
 nd ways to get away from the email patch model".\n\nWhile the community is
  researching and arguing about alternatives\, we'll take a look at just on
 e of them – GitLab – and how it already helps some maintainers and dev
 elopers in or near the kernel community to smoothly integrate testing into
  their workflow.\n\nWe'll talk about our use of GitLab at Red Hat's CKI\, 
 explore DRM CI\, Mesa3D CI\, Media-CI\, and the proposal we worked on at K
 ernelCI to introduce the standard GitLab CI pipeline into the kernel. We'l
 l look at what they're already doing\, what they can enable in the future\
 , and which part they can play in replacing the email workflow.
LOCATION:E112 (capacity 156)
URL:https://pretalx.com/devconf-cz-2024/talk/NMQDGE/
END:VEVENT
END:VCALENDAR