BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.devconf.info//devconf-us-2026//talk//TUQZQJ
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-devconf-us-2026-TUQZQJ@pretalx.devconf.info
DTSTART;TZID=EST:20260924T144000
DTEND;TZID=EST:20260924T145500
DESCRIPTION:You don’t jump ~1\,197 spots on the PyTorch contributor leade
 rboard by accident. It was our PyTorch Engineering Team that did the high-
 speed driving—writing\, refining\, and getting their code merged to make
  this massive leap possible. This talk pulls back the curtain on how the t
 eam evolved their day-to-day practices to scale our open-source footprint.
  I’ll share how our developers streamlined community contributions\, rem
 oved friction for external collaborators\, and adapted their internal Agil
 e workflows to match the breakneck speed of the broader PyTorch ecosystem.
  If you want to amplify your own organization’s open-source impact\, com
 e see how a async-first workflow transformed from a process requirement in
 to a massive competitive advantage.
DTSTAMP:20260727T175018Z
LOCATION:Hewitt Boardroom (Capacity 35)
SUMMARY:The Climb Nobody Expected: From ~#1200 to #3 rank on the PyTorch Le
 aderboard - Saiesh Prabhu
URL:https://pretalx.devconf.info/devconf-us-2026/talk/TUQZQJ/
END:VEVENT
END:VCALENDAR