BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.evolutio.pt//ZY8UHF
BEGIN:VTIMEZONE
TZID:EET
BEGIN:STANDARD
DTSTART:20001029T050000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:EET
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:EEST
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-djangocon-europe-2026-ZY8UHF@pretalx.evolutio.pt
DTSTART;TZID=EET:20260415T110000
DTEND;TZID=EET:20260415T113000
DESCRIPTION:Ever thought about what happens when someone finds a security i
 ssue in Django? How do you disclose an issue responsibly? What happens aft
 er that? How does the Django team work on it? What happens until a securit
 y release is published? What comes afterward? And what impact have AI and 
 LLMs on Django and its security?
DTSTAMP:20260502T014931Z
LOCATION:AMPHITHEATRE
SUMMARY:Oh\, I Found a Security Issue - Markus Holtermann
URL:https://pretalx.evolutio.pt/djangocon-europe-2026/talk/ZY8UHF/
END:VEVENT
END:VCALENDAR