BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//scipy-2026//talk//HXFDCX
BEGIN:VTIMEZONE
TZID:CST
BEGIN:STANDARD
DTSTART:20001029T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T080000Z
TZNAME:CST
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
END:STANDARD
BEGIN:STANDARD
DTSTART:20071104T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:CST
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000402T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T090000Z
TZNAME:CDT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T030000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:CDT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-scipy-2026-HXFDCX@pretalx.com
DTSTART;TZID=CST:20260717T104500
DTEND;TZID=CST:20260717T111500
DESCRIPTION:Nobody loves writing release notes... and it only gets worse wh
 en multiple institutions are editing the same file. We learned the hard wa
 y that using a single file\, manual RST editing\, and no validation leads 
 to repeated merge conflicts every release cycle. In response\, we built Br
 assy\, a CLI tool that replaces single-file changelogs with per-change YAM
 L files\, assembles them into formatted release notes\, and lints entries 
 in CI. We also built PinkRST (an RST formatter) and a Python-based Sphinx 
 build system to tie our large multi-institution and many repo software doc
 umentation together. This talk covers the tools\, the integration\, and wh
 at we learned about getting scientists to _actually_ write documentation.
DTSTAMP:20260715T023025Z
LOCATION:Thomas Swain Room
SUMMARY:Brassy: Palatable Multi-Institution Release Notes - Gwyn Uttmark
URL:https://pretalx.com/scipy-2026/talk/HXFDCX/
END:VEVENT
END:VCALENDAR