BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//events.eurobsdcon.org//2026//talk//EA98CK
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-2026-EA98CK@events.eurobsdcon.org
DTSTART;TZID=CET:20260913T103000
DTEND;TZID=CET:20260913T111500
DESCRIPTION:In June 2026\, the FreeBSD entries in dozens of upstream `.cirr
 us.yml` files became dead code. For roughly five years\, Cirrus CI had bee
 n doing\; almost invisibly\; what FreeBSD's own internal CI was never desi
 gned to do: making it trivial for upstream open-source projects (LLVM\, Ru
 st\, Python\, PHP\, Node.js\, libuv\, curl\, and others) to test their sof
 tware against FreeBSD on every pull request\, with no infrastructure for t
 hem to operate. That capability is now gone. Nothing in the current market
  replaces it.\n\nThis talk argues that FreeBSD's adoption ceiling is set b
 y whether upstreams can test on FreeBSD\; not just by whether we can test 
 FreeBSD ourselves. It works through four threads: what Cirrus quietly solv
 ed between 2019 and 2026\, and why most of the community didn't notice\; t
 he current landscape of partial substitutes (vmactions/freebsd-vm\, self-h
 osted Jenkins\, the GitHub Actions BSD gap\, the in-tree pre-commit toolin
 g) and why none of them fits the shape of the upstream-facing problem\; wh
 y no individual developer can plug this gap\, and why this is a company-sc
 ale problem rather than a hobby one\; and what FreeBSD is already paying f
 or the absence\; in enterprise procurement conversations\, contributor att
 rition\, and quiet drop-outs in upstream release notes.\n\nThe talk closes
  with a five-point specification for what a viable successor would have to
  look like\, and asks three groups in the room for specific action: the Fr
 eeBSD community\, the Foundation and enterprise users\, and the upstream m
 aintainers themselves.\n\nForty minutes\; five for questions. Technical\, 
 opinionated\, assumes the audience knows what make buildworld does.
DTSTAMP:20260715T130205Z
LOCATION:D.0.02
SUMMARY:make buildworld && make install-future: Why FreeBSD's Adoption Stor
 y Runs Through Continuous Integration - Moin Rahman
URL:https://events.eurobsdcon.org/2026/talk/EA98CK/
END:VEVENT
END:VCALENDAR
