BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.fedoraproject.org//flock-2024//talk//WTQXLH
BEGIN:VTIMEZONE
TZID:EST
BEGIN:STANDARD
DTSTART:20001029T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T070000Z
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:STANDARD
DTSTART:20071104T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000402T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T080000Z
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T030000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-flock-2024-WTQXLH@cfp.fedoraproject.org
DTSTART;TZID=EST:20240808T140000
DTEND;TZID=EST:20240808T145500
DESCRIPTION:What hides behind the process of making quality Fedora releases
 ? How\, and why can you contribute? How CI gating\, blocker bugs\, common 
 bugs\, validation matrices\, blocker reviews\, and go/no-go meetings work?
  How does the freeze process work? How do all these parts fit together?\n\
 nHow can anybody help a tiny bit to make the final releases as rock-stable
  as possible for as many hardware as possible? We'll get through all the i
 mportant bits of the Quality Assurance of Fedora releases with a bit of sh
 owcasing for each of the sections\, so you'll see under the hood how we wo
 rk and you'll be able to help with ensuring and improving your life for yo
 ur use-cases of the distribution.
DTSTAMP:20261115T152307Z
LOCATION:Rocky (Breakout 2)
SUMMARY:How to be a superhero... of Fedora Quality! - Frantisek Zatloukal\,
  Lukáš Růžička
URL:https://cfp.fedoraproject.org/flock-2024/talk/WTQXLH/
END:VEVENT
END:VCALENDAR
