BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.northbaypython.org//nbpy-2026//T7NNU3
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-2026-QHBEE9@pretalx.northbaypython.org
DTSTART;TZID=PST:20260426T141500
DTEND;TZID=PST:20260426T144000
DESCRIPTION:Sometimes we set out to create a project with clearly defined s
 cope\, with the best of intentions for maintainability\, usability\, and c
 larity. Then\, if we’re lucky\, users show up and want to do something e
 lse. It starts small - a feature here\, an edge case there. How do we navi
 gate ‘scope creep’ in open source projects and the tension between wha
 t we set out to build\, what we can competently maintain\, and what users 
 actually want? Told through the history of JupyterHub\, a project for host
 ing Jupyter notebook servers targeted explicitly at small single-machine g
 roups\, which is now used routinely to serve thousands of students and res
 earchers\; something which was explicitly and deliberately out of scope fo
 r the project from day 1. But users want what they want.
DTSTAMP:20260404T061333Z
LOCATION:Barn
SUMMARY:No Project Scope Survives Contact with Users - Min Ragan-Kelley
URL:https://pretalx.northbaypython.org/nbpy-2026/talk/QHBEE9/
END:VEVENT
END:VCALENDAR