BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.northbaypython.org//8RZXD9
BEGIN:VTIMEZONE
TZID:PST
BEGIN:STANDARD
DTSTART:20001029T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T100000Z
TZNAME:PST
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
END:STANDARD
BEGIN:STANDARD
DTSTART:20071104T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:PST
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000402T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T110000Z
TZNAME:PDT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T030000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:PDT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-nbpy-2024-8RZXD9@pretalx.northbaypython.org
DTSTART;TZID=PST:20240629T151500
DTEND;TZID=PST:20240629T154000
DESCRIPTION:We’re hopefully all on board with writing documentation for o
 ur projects. However\, especially with the rise of supply-chain attacks\, 
 there are some aspects of our projects that we really shouldn’t document
 \, and should instead remediate as vulnerabilities. If we do document thes
 e aspects of a project\, it may help someone compromise the project itself
  or our users. In this talk\, you will learn why some aspects of documenta
 tion may help attackers more than users\, how to recognize those aspects i
 n your own projects\, and what to do when you encounter such an issue.
DTSTAMP:20260717T134455Z
LOCATION:Barn
SUMMARY:What Not To Document And Why - Margaret Fero
URL:https://pretalx.northbaypython.org/nbpy-2024/talk/8RZXD9/
END:VEVENT
END:VCALENDAR