2409 lines
112 KiB
Text
2409 lines
112 KiB
Text
|
|
BEGIN:VCALENDAR
|
|||
|
|
VERSION:2.0
|
|||
|
|
PRODID:-//2025.fossy.us/schedule//EN
|
|||
|
|
CALSCALE:GREGORIAN
|
|||
|
|
METHOD:PUBLISH
|
|||
|
|
X-WR-CALDESC:FOSSY 2024
|
|||
|
|
X-WR-TIMEZONE:US/Pacific
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Coffee/tea break
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T091500
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T094500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:234@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Breakfast and coffee break
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Coffee/tea break
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T091500
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T094500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:233@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Breakfast and coffee break
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Coffee/tea break
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T091500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T094500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:232@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Breakfast and coffee break
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Assessing and Managing threats to the Nonprofit Infrastructure of
|
|||
|
|
FOSS
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T094500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T102500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:229@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Allen Gunn\nFree and Open Source Software has long r
|
|||
|
|
elied on a robust network of nonprofit organizations set up to support its
|
|||
|
|
development and advocacy. In recent years\, this infrastructure has been
|
|||
|
|
tested as funding has declined and the uncertainties related to running th
|
|||
|
|
ese organizations have increased\, resulting in closures or reductions in
|
|||
|
|
staff at many orgs. In this keynote\, Pono Takamori will host a conversati
|
|||
|
|
on with Allen Gunn of Aspiration about the current challenges facing fisca
|
|||
|
|
l sponsorship organizations\, how the decline in funding for these organiz
|
|||
|
|
ations will impact FOSS generally and how to assess a variety of threats
|
|||
|
|
in the US and globally..
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/362/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSS in A/V: How Open Signal uses FOSS to further their mission in
|
|||
|
|
a closed source industry
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T094500
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T103000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:231@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Chris Polanco\nOpen Signal is a media arts center in
|
|||
|
|
Portland\, Oregon\, with a mission\nto nurture the change-making power of
|
|||
|
|
community media in service of a\njust and equitable world. In this convers
|
|||
|
|
ation with Chris Polanco\, their\nProduction Services Production Manager\,
|
|||
|
|
we'll talk about how and why\nOpen Signal chooses open source as much as
|
|||
|
|
they can in a world of SaaS\nand proprietary products. They do this not ju
|
|||
|
|
st while partnering with\nus to do audio/video for FOSSY\, but across thei
|
|||
|
|
r work with local youth\nand other media makers. We'll talk about some of
|
|||
|
|
the hardware and\nsoftware they use\, how those choices are informed by th
|
|||
|
|
eir mission\,\nand what sort of future they are working toward.
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/367/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Q&A on SFC's lawsuit against Vizio
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T094500
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T103000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:230@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Bradley M. Kuhn\nThere's a reason that some of the mo
|
|||
|
|
st popular shows on television for generations have been courtroom dramas.
|
|||
|
|
Court cases are dramatic by their nature!\n\nCome ask us anything at all
|
|||
|
|
about the Software Freedom Conservancy's lawsuit against Vizio. The tria
|
|||
|
|
l is only 6 weeks away\, so hear about everything and get yourself ready t
|
|||
|
|
o go down to Los Angeles and attend the trial.
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/365/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Registration
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T101500
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T131500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:239@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Registration Open
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Keynote Session
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T102500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T103500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:398@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Presentation of the Distinguished Service Award in Software Fr
|
|||
|
|
eedom
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Lightning Talks!
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T103000
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T123000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:386@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Pono Takamori\n1. Vagrant Cascadian: An Impatient App
|
|||
|
|
lication of Reproducible Builds\n2. Josh Lee: The OSS Hero's Journey\n3. J
|
|||
|
|
ulia Zimmerman: Quantifying Sky Signals: Simulating Visibility Correlation
|
|||
|
|
s in Radio Interferometry\n4. Zhi Qu: BLuE CRAB: RSSI Detection Pattern An
|
|||
|
|
alysis for Flagging System Development\n5. Andrew Washburn: Using Quantum
|
|||
|
|
Computers to Detect Continuous Gravitational Waves\n6. Audrey Evergreen: A
|
|||
|
|
voiding Desk Neck While Coding\n7. Neal Gompa: X.Org Foundation and SFC\n8
|
|||
|
|
. Mark Davis: H.U.G.E. Announcement\n9. Alya Abbott: Choosing Software tha
|
|||
|
|
t Won't Screw You\n10. Emily Soward: What and Why we Need AI Preparedness\
|
|||
|
|
n11. Brendan Conoboy: Command Line Control\n12. Eric Schultz: Glasgow Embe
|
|||
|
|
dded Code of Conduct
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/368/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:PostgreSQL’s Rise to Power: Why the Open Source Giant is Dominat
|
|||
|
|
ing the Database Landscape
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T104500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T113000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:285@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Kellyn Gorman\nPostgreSQL has quietly\, but powerfull
|
|||
|
|
y risen to become one of the most trusted and widely adopted database plat
|
|||
|
|
forms in the world. Once considered a niche solution back in it's days as
|
|||
|
|
it's predecessor\, Ingres\, PostgreSQL now leads the charge in the open-so
|
|||
|
|
urce database movement\, challenging and often surpassing traditional ente
|
|||
|
|
rprise heavyweights like Oracle and SQL Server. \nIn this session\, we’l
|
|||
|
|
l explore the technical\, strategic\, and cultural reasons behind PostgreS
|
|||
|
|
QL’s rapid ascent. From its robust standards compliance and extensibilit
|
|||
|
|
y to its vibrant development community and compatibility with modern cloud
|
|||
|
|
-native architectures\, PostgreSQL delivers enterprise-grade performance w
|
|||
|
|
ithout the steep licensing costs. \nWe'll also examine how PostgreSQL’s
|
|||
|
|
innovation is influencing other platforms like MySQL\, MongoDB\, and SQLit
|
|||
|
|
e\, and why developers and architects are increasingly choosing it as the
|
|||
|
|
foundation for their mission-critical workloads. This session will cover
|
|||
|
|
everything from high availability options\, most popular extensions and fe
|
|||
|
|
atures that keep PostgreSQL the choice among database technologists\, no m
|
|||
|
|
atter if traditional transactional\, analytical or even AI workloads. We'
|
|||
|
|
ll also discuss the limitations around migrations and how to best take on
|
|||
|
|
the challenges or moving large\, enterprise\, multi-tier systems over to o
|
|||
|
|
pen-source solutions.\nWhether you're considering migration\, multiplatfor
|
|||
|
|
m strategy\, or just want to understand the open-source momentum\, this se
|
|||
|
|
ssion will provide deep insights into PostgreSQL’s success and what it m
|
|||
|
|
eans for the future of data.
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/289/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Things I've Learned as a Linux Kernel Maintainer
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T104500
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T113000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:347@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Darrick J. Wong\nI spent seven years serving as the m
|
|||
|
|
aintainer of the XFS filesystem and iomap filesystem library in the Linux
|
|||
|
|
kernel. Whilst on that journey\, I learned a lot about steering technical
|
|||
|
|
direction of those two projects\, but also the limitations of managing a
|
|||
|
|
community without authority. I intend this talk to be most helpful for pe
|
|||
|
|
ople who are current FOSS maintainers or are mid to senior level developer
|
|||
|
|
s contemplating taking on such roles.\n\nThese are the seven skills that I
|
|||
|
|
found most helpful and grew the most in those seven years:\n * Concocting
|
|||
|
|
a strategy from which to build a development roadmap\n * Defining roles f
|
|||
|
|
or people to take on\n * Negotiating staffing and budgets with managers\n
|
|||
|
|
* Coaching people who are trying to get their efforts across the finish li
|
|||
|
|
ne\n * Dealing with external shocks in as principled a manner as possible\
|
|||
|
|
n * Steering your way out of burnout\, aka Replacing Yourself\n * Supporti
|
|||
|
|
ng\, but getting out of the way of\, the new leaders you cultivate\n\nFor
|
|||
|
|
each of these areas\, I'll share how that skill fits into the Linux commun
|
|||
|
|
ity (they didn't always fit well!) and what happened when I tried to make
|
|||
|
|
things happen in those areas. I will target spending about 4-5 minutes ta
|
|||
|
|
lking about each of those points and leave 20-25 minutes at the end for an
|
|||
|
|
audience discussion.
|
|||
|
|
LOCATION:333
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/345/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Discussion: Which Way Do We Go? Understanding Sustainable Pathways
|
|||
|
|
for Academic Open Source
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T104500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T113000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:297@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Stephanie Lieggi\nNote: this will be a group discussi
|
|||
|
|
on format with participation from anyone who wishes to join.\n\nMany impac
|
|||
|
|
tful open source projects begin as ideas in academic research labs\, as hi
|
|||
|
|
ghlighted by the wide adoption of projects like Ceph\, RISC-V and Jupyter.
|
|||
|
|
However\, so much of what is created in universities doesn’t find broad
|
|||
|
|
er adoption and struggles to be sustainable in the long-term. This is a lo
|
|||
|
|
st opportunity that can have a broad impact on scientific communities\, in
|
|||
|
|
dustry and society at large. This BoF session aims to explore the differen
|
|||
|
|
t pathways for academic open source projects to find their way to sustaina
|
|||
|
|
bility and adoption. As with most things open source – there is no one-s
|
|||
|
|
ize-fits-all. This session will provide those with experience in building
|
|||
|
|
and maintaining academic open source projects an opportunity to share that
|
|||
|
|
experience with those looking for the right pathway for their own project
|
|||
|
|
. It will also provide those working or supporting academic Open Source Pr
|
|||
|
|
ogram Offices (OSPOs) an opportunity to highlight how they are helping pro
|
|||
|
|
jects on their campus become sustainable and best serve the research and e
|
|||
|
|
ducational goals of their institutions.
|
|||
|
|
LOCATION:329
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/335/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Talk
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T104500
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T113000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:331@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:328
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Open Source Software in Higher Education: A Community Report
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T104500
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T113000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:338@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Patrick Masson\nReports highlighting the adoption of
|
|||
|
|
open source software (OSS) are ubiquitous. Yet studies specific to higher
|
|||
|
|
education are limited\, perhaps leaving campuses unprepared to manage thei
|
|||
|
|
r edtech portfolios.\n\nThe Apereo Foundation\, in partnership with other
|
|||
|
|
open source software foundations and global universities\, will present pr
|
|||
|
|
eliminary data from the Open Source Software in Higher Education Community
|
|||
|
|
Report. This report offers unique insights into the perceptions of OSS di
|
|||
|
|
scovered through a survey of IT leaders undertaken at EDUCAUSE 2025\, as w
|
|||
|
|
ell as the prevalence of OSS in use across academic enterprises through pr
|
|||
|
|
ofiling and analysis of .edu domains. The 2025 data is then compared to hi
|
|||
|
|
storical data to provide historical trends\, compare current practices\, a
|
|||
|
|
nd identify areas of future impact.
|
|||
|
|
LOCATION:329
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/329/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Never Mind the Checkboxes\, Here's Reproducible Builds!
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T104500
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T113000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:314@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Vagrant Cascadian\nThere are numerous policy complian
|
|||
|
|
ce and regulatory processes being developed that target software developme
|
|||
|
|
nt... but do they solve actual problems? Does it improve the quality of so
|
|||
|
|
ftware? Do Software Bill of Materials (SBOMs) actually give you the inform
|
|||
|
|
ation necessary to verify how a given software artifact was built? What is
|
|||
|
|
the goal of all these compliance checklists anyways... or more importantl
|
|||
|
|
y\, what *should* the goals be? If a software object is signed\, who shoul
|
|||
|
|
d be trusted to sign it\, and can they be trusted ... forever?\n\nCould yo
|
|||
|
|
u imagine a world with many bureaucratic compliance checks being replaced
|
|||
|
|
with verifiable processes performed by arbitrary third parties?\n\nLet me
|
|||
|
|
introduce you to Reproducible Builds\, a set of best practices which allow
|
|||
|
|
you to verify that software artifacts were built from the source code\, a
|
|||
|
|
llowing auditing for license compliance\, providing security benefits\, an
|
|||
|
|
d remove the need to trust arbitrary software vendors.
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/327/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Starting an Open Mentorship Handbook!
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T104500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T113000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:307@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Pono Takamori\nTechnology communities committed to tr
|
|||
|
|
ansparency and openness (like free and open source software\, or FOSS\, co
|
|||
|
|
mmunities) adopt sets of practices to facilitate their collaboration. In o
|
|||
|
|
rder to work together developing software\, practicing open science and fa
|
|||
|
|
cilitating open data\, collaborators must build robust communities to publ
|
|||
|
|
icly discuss and improve their projects. Healthy communities that continu
|
|||
|
|
e productively into the future must find ways to engage and nurture new co
|
|||
|
|
ntributors in order to maintain and grow their communities. Some communiti
|
|||
|
|
es struggle to attract new contrinbutors in the first place\, while other
|
|||
|
|
communities attract many new contributors\, but struggle to coach those co
|
|||
|
|
ntributors on how to become leaders\, reviewers\, and maintainers of their
|
|||
|
|
community's work.\n\nOpen mentorship programs provide a safe space for in
|
|||
|
|
terns to learn how to work in an open\, public manner with open communitie
|
|||
|
|
s\, and how to create and maintain public works. Unfortunately\, documenta
|
|||
|
|
tion on how to be a mentor in an open mentorship program is often non-exis
|
|||
|
|
tent\, out of date\, or scattered across many different resources. The Out
|
|||
|
|
reachy team is launching an Open Mentorship Handbook\, to gather best prac
|
|||
|
|
tices in mentorship and to provide a collaborative way to share the knowle
|
|||
|
|
dge that we've amassed in this area.\n\nCome learn about this initiative a
|
|||
|
|
nd participate in a collaborative session about the Handbook and Open ment
|
|||
|
|
orship!
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/358/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:How do sponsored open source ecosystems manage feature deployments
|
|||
|
|
?
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T104500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T113000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:291@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Matt Gaughan\nThe academic study of FOSS libraries of
|
|||
|
|
ten assumes that projects are organized as communities of volunteer contri
|
|||
|
|
butors. However\, the recent growth of sponsored open source libraries ---
|
|||
|
|
projects stewarded by large\, formally incorporated organizations --- pro
|
|||
|
|
vides new organizational relationships and processes to better understand
|
|||
|
|
. One common form of this is constructed when an organization stewards a l
|
|||
|
|
ibrary while also managing the library's primary implementation\; in this
|
|||
|
|
model\, decision making around the library and its implementation are deep
|
|||
|
|
ly interconnected\, yet may be governed differently. Examples of this mode
|
|||
|
|
l include Apple’s use of WebKit in Safari\, BlueSky’s use of ATProto i
|
|||
|
|
n BlueSky applications\, and the WikiMedia Foundation’s (WMF) use of Med
|
|||
|
|
iaWiki libraries in\nWikimedia platforms. This ongoing work focuses on thr
|
|||
|
|
ee feature deployments on Wikimedia platforms\, examining deployment proce
|
|||
|
|
sses' impacts on the MediaWiki libraries utilized for feature development.
|
|||
|
|
By analyzing commit activity\, work tasks\, and community discussions\, w
|
|||
|
|
e provide greater insight into how certain deployment processes impact the
|
|||
|
|
open source development of a critical open platform.
|
|||
|
|
LOCATION:333
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/350/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Talk
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T104500
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T113000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:353@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Herding Hackers and Hawking Code: The Hustle of a Developer Advoca
|
|||
|
|
te
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T104500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T113000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:327@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Nate Boot\nYou may have heard of a developer advocate
|
|||
|
|
. You might have even seen one on stage or met one at a conference booth s
|
|||
|
|
linging stickers like they’re currency. Odds are you’ve probably seen
|
|||
|
|
a YouTube video or read a blog post from a developer advocate\, talking ab
|
|||
|
|
out why an API has changed or acting as an “explainer of stuff” for so
|
|||
|
|
me new feature. Our lives are never boring\, but how can you tell if it’
|
|||
|
|
s something you’d be interested in? Just what else are these folk up to?
|
|||
|
|
\n\nThey are a must have if your particular open source project has regul
|
|||
|
|
ar user groups. You might even consider them a kind of translation layer.
|
|||
|
|
You see\, they usually have backgrounds in software engineering but instea
|
|||
|
|
d of coding all day\, they're likely to be found talking about code all da
|
|||
|
|
y. When your users are suffering from deficiencies and bring them to user
|
|||
|
|
groups to be discussed\, these advocates can usually pinpoint what group o
|
|||
|
|
f developers and/or repositories those code changes need to be made in. Th
|
|||
|
|
ey are a bridge between development teams and user communities.\n\nI’d l
|
|||
|
|
ove a chance to share my experience. If you have a passion for open source
|
|||
|
|
projects and want to someday get involved in a pragmatic and supportive w
|
|||
|
|
ay\, let me take you through my journey and share just what makes it speci
|
|||
|
|
al to me and why it makes such a difference to the community of any open s
|
|||
|
|
ource product.
|
|||
|
|
LOCATION:328
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/296/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Break
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T113000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T114500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:269@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Break
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T113000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T114500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:270@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Talk
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T114500
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T123000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:354@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Reimagining Online Deliberation: Why Open Source is Critical for C
|
|||
|
|
ivic Infrastructure
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T114500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T123000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:305@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Samantha Shireman\nWhat if the tools we use for civic
|
|||
|
|
engagement were as common as Google Docs\, but built on open source princ
|
|||
|
|
iples? In today's polarized digital landscape\, creating space for thought
|
|||
|
|
ful\, inclusive dialogue is more critical than ever.\n \nWithin Harvard's
|
|||
|
|
Berkman Klein Center\, our Applied Social Media Lab is building Frankly\,
|
|||
|
|
an open source video-based discourse platform that structures online face-
|
|||
|
|
to-face conversations for meaningful outcomes.\nIt combines intelligent gr
|
|||
|
|
oup matching with embedded discussion prompts\, enabling balanced groups t
|
|||
|
|
o navigate complex topics without facilitators in order to make constructi
|
|||
|
|
ve discourse and collaborative decision-making accessible and scalable.\n
|
|||
|
|
\nThis session explores how we’re rethinking online discourse to better
|
|||
|
|
support civic engagement and social connection\, and why democratic infras
|
|||
|
|
tructure must be built on open source principles. Open source enables adap
|
|||
|
|
tability to different contexts\, ensures longevity beyond any single insti
|
|||
|
|
tution\, and provides the scrutinizability necessary for legitimate public
|
|||
|
|
discourse.\n \nBy open-sourcing Frankly and collaborating with practition
|
|||
|
|
ers\, we're developing civic technology that is transparent\, adaptable\,
|
|||
|
|
and grounded in dialogue expertise. As we increasingly make collective dec
|
|||
|
|
isions in digital spaces\, building deliberative infrastructure on open fo
|
|||
|
|
undations isn't just technically superior—it's democratically essential.
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/328/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:More Scalability Through Open Source Hygiene
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T114500
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T123000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:326@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Ria Farrell Schalnat\nAs more attention is paid to SB
|
|||
|
|
OMs through Executive Orders in the United States and legislation like the
|
|||
|
|
European Union's Cyber Resilience Act\, being able to ingest\, identify\,
|
|||
|
|
evaluate and approve open source packages will be critical to scaling com
|
|||
|
|
pliance operations as well as empowering developers by giving them an earl
|
|||
|
|
y heads up on the choices they are making in their solutions. SPDX identi
|
|||
|
|
fiers provide a quick identification mechanism for the license utilized by
|
|||
|
|
a component. ClearlyDefined provides important provenance data includin
|
|||
|
|
g component source locations\, licensing\, attributions and more. GUAC p
|
|||
|
|
rovides tooling to enhance SBOMs with security and vulnerability data. CH
|
|||
|
|
AOSS provides health metrics associated with open source components. All
|
|||
|
|
of these projects allow the development of policies and empower developer
|
|||
|
|
s to align their choices with personal or company preferences. This ses
|
|||
|
|
sion will touch on all these projects and then walk through the process to
|
|||
|
|
assign an SPDX-ID to a license. When you leave\, you'll know how to enga
|
|||
|
|
ge with the SPDX-Legal committee and how to respond to issues in their rep
|
|||
|
|
o to get IDs assigned to licenses. Help US to help YOU to scale your open
|
|||
|
|
source compliance!
|
|||
|
|
LOCATION:328
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/364/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Power Dynamics\, Rug Pulls\, and Other Impacts on FOSS Sustainabil
|
|||
|
|
ity
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T114500
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T123000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:348@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Dr. Dawn Foster\nPower imbalances are everywhere\, in
|
|||
|
|
cluding in our FOSS projects. Corporations hold power over projects that r
|
|||
|
|
esult in relicensing\, forks\, and other disruptions. This talk will cover
|
|||
|
|
these power dynamics using research data from several case study projects
|
|||
|
|
and suggest steps that we can take to make better decisions about which F
|
|||
|
|
OSS projects to embrace.\n\nSince the beginning of time\, those in power h
|
|||
|
|
ave been able to use that power against the weak\, often with little recou
|
|||
|
|
rse. In feudalism\, the powerful ruling class controlled the land leading
|
|||
|
|
to oppression and exploitation of the people doing the hard work of farmin
|
|||
|
|
g and protecting the land. This may sound familiar\, since many FOSS proje
|
|||
|
|
cts similarly have the power consolidated in the hands of the few even whe
|
|||
|
|
n others with less power are doing most of the work. In today’s cloud na
|
|||
|
|
tive world\, the power dynamics have gotten even more complex. Large cloud
|
|||
|
|
providers have the most power and can create service offerings based sole
|
|||
|
|
ly on FOSS projects while doing little to no real work on those projects.
|
|||
|
|
Smaller companies who are doing a significant amount of the development on
|
|||
|
|
a FOSS project have less power than the cloud providers\, but many still
|
|||
|
|
have the power to relicense those projects. The many users\, contributors\
|
|||
|
|
, and even maintainers who have less power can feel like the rug has been
|
|||
|
|
pulled out from under them. We’ve recently seen an increase in relicensi
|
|||
|
|
ng of FOSS projects and other tensions within communities that are directl
|
|||
|
|
y related to imbalances in power that cause disruption within our projects
|
|||
|
|
.\n \nWe have mechanisms\, like forks\, where those with less power can co
|
|||
|
|
unter these power moves\, regardless of the forms they take. The Elasticse
|
|||
|
|
arch\, Redis\, and Terraform relicensing resulted in the OpenSearch\, Valk
|
|||
|
|
ey\, and OpenTofu forks. As part of an ongoing 1+ year research effort und
|
|||
|
|
er the CHAOSS project\, this talk will dive into the data for these six pr
|
|||
|
|
ojects to illustrate these power dynamics.\n\nAs maintainers\, contributor
|
|||
|
|
s\, and users of FOSS\, we devote our most precious resource to these proj
|
|||
|
|
ects\, time. We need for the projects that we spend time on to be sustaina
|
|||
|
|
ble over the long term to avoid wasting this precious resource. There is n
|
|||
|
|
o way to predict which projects will be sustained over time\, but this tal
|
|||
|
|
k will contain detailed suggestions for how to look for warning signs. Who
|
|||
|
|
holds the power in the FOSS projects that we use and contribute to? How d
|
|||
|
|
o they use that power? What governance processes are in place to provide c
|
|||
|
|
hecks and balances to avoid the misuse of that power? Beyond identifying w
|
|||
|
|
arning signs\, this talk will contain suggestions for how we can work with
|
|||
|
|
in projects to help them become more sustainable. This talk will not only
|
|||
|
|
help people understand the power dynamics at play\, but will also provide
|
|||
|
|
tangible steps that we can take as maintainers\, contributors\, and users
|
|||
|
|
to make better decisions about focusing our precious time on making our pr
|
|||
|
|
ojects more sustainable.
|
|||
|
|
LOCATION:333
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/342/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:DRM\, security\, or both? How do we decide?
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T114500
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T123000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:306@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Matthew Garrett\nAn easy way to define malware is "So
|
|||
|
|
ftware that I don't want running on my computer". And one way to ensure th
|
|||
|
|
at you're protected from malware would be to ensure that your computer onl
|
|||
|
|
y runs software you want to run. But how is technology that allows that di
|
|||
|
|
fferent to technology that allows someone *else* to choose what software y
|
|||
|
|
our computer runs? Someone who isn't necessarily motivated by your best in
|
|||
|
|
terests? How do we decide what is security\, and how do we decide what is
|
|||
|
|
DRM?\n\nThis presentation will cover various technologies that allow gener
|
|||
|
|
al purpose computers to become less general purpose\, and discuss whether
|
|||
|
|
they are of net benefit to users or a net risk to their freedoms. It will
|
|||
|
|
discuss whether TPMs are actually locking you down\, whether secure boot h
|
|||
|
|
as been a success or a failure\, how immutable distros and app packaging p
|
|||
|
|
lay into this\, and give you some hope that we can take the tools that wer
|
|||
|
|
e made to restrict us and repurpose them to protect us.
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/325/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:The Creative Trade-Off: Governance\, Conflict\, and Their Impact O
|
|||
|
|
n Innovation In Open-Source Software
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T114500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T123000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:292@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Dr. Justin Ribeiro\, PhD\nSoftware development has al
|
|||
|
|
ways been fueled by creativity but today\, efficiency metrics\, process-he
|
|||
|
|
avy methods\, and the rise of AI now often box that creativity out. While
|
|||
|
|
developers are drawn to solving tough problems\, modern practices can unin
|
|||
|
|
tentionally prioritize small tweaks over bold breakthroughs. This tension
|
|||
|
|
risks limiting not just individual potential\, but open source’s ability
|
|||
|
|
to drive meaningful innovation.\n\nIn this talk\, we dive into how develo
|
|||
|
|
pment approaches shape creativity at the project level\, drawing from a st
|
|||
|
|
udy of 40 open source projects\, over 10\,000 releases\, and interviews wi
|
|||
|
|
th developers across corporate and community-run efforts. Using multi-leve
|
|||
|
|
l creativity theories\, we unpack how individual actions\, team interactio
|
|||
|
|
ns\, and project governance can either spark or stifle innovative outcomes
|
|||
|
|
.\n\nOur research challenges the myth of the lone “rockstar” developer
|
|||
|
|
and highlights the crucial role of social interactions within the open so
|
|||
|
|
urce community— especially during review stages such as pull requests an
|
|||
|
|
d code reviews—in turning creative ideas into real-world innovations. We
|
|||
|
|
show how cognitive conflict and governance models impact creative outcome
|
|||
|
|
s and offer strategies for building more innovative\, collaborative open s
|
|||
|
|
ource projects and communities.\nIf we want open source to keep leading th
|
|||
|
|
e way\, we need development practices that empower creativity\, not constr
|
|||
|
|
ain it. Let’s rethink how we build and unlock a more radical future for
|
|||
|
|
open source software.
|
|||
|
|
LOCATION:333
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/347/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Empowering Teams in Open Source EdTech Communities
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T114500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T123000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:298@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Joshua Wilson\nJoin us to explore how Google's Projec
|
|||
|
|
t Aristotle findings can empower teams of developers and educators in open
|
|||
|
|
source educational technology. Through interactive exercises\, you'll lea
|
|||
|
|
rn practical techniques for making teams more effective by ensuring equal
|
|||
|
|
voice in feature discussions and developing social sensitivity in asynchro
|
|||
|
|
nous communication. You'll leave with concrete strategies to build a team
|
|||
|
|
dynamic that supports your FOSS project and create psychological safety th
|
|||
|
|
at enables both developers and educators to admit knowledge gaps and learn
|
|||
|
|
from each other.
|
|||
|
|
LOCATION:329
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/336/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Up Against the WAL: The Write-Ahead Log in PostgreSQL
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T114500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T123000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:286@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Christophe Pettus\nThe Write-Ahead Log in PostgreSQL
|
|||
|
|
underlies a huge number of features: crash recovery\, binary replication\,
|
|||
|
|
logical replication\, and backups. This talk is a dive into the internals
|
|||
|
|
of the WAL\, including its format\, how it is written to storage\, how it
|
|||
|
|
is used\, and what to do when you get one of the many terrifying errors a
|
|||
|
|
bout WAL issues.
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/355/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Raising the bar on your conference presentation
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T114500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T123000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:325@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Rich Bowen\nWe've all attended - or given - presentat
|
|||
|
|
ions that put the audience to sleep\, or at least had most of them playing
|
|||
|
|
Kwazy Cupcakes on their phones. In this presentation\, we talk about ways
|
|||
|
|
that you can improve your conference presentations by making a few simple
|
|||
|
|
changes.\n\nYou know the presentations I'm talking about. The slides are
|
|||
|
|
73 lines of 12-point font\, and the speaker reads them to you with their b
|
|||
|
|
ack turned. Ok\, maybe not that bad. But you want to leave the audience wa
|
|||
|
|
nting more\, and eager to take the next step. Here's a few simple tips for
|
|||
|
|
making your conference and meetup presentations engaging\, rather than so
|
|||
|
|
porific.
|
|||
|
|
LOCATION:328
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/282/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Talk
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T114500
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T123000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:337@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:329
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Lunch break (on your own)
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T123000
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T134500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:226@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:<em>Lunch break (on your own)</em>
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Lunch break (on your own)
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T123000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T140000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:224@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:<em>Lunch break (on your own)</em>
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Lunch break (on your own)
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T123000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T140000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:225@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:<em>Lunch break (on your own)</em>
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Opening Remarks
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T134500
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T140000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:227@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Opening Remarks
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Intro to Unconferences
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T134500
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T140000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:397@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Aaron Wolf\nAn unconference fits a middle-ground betw
|
|||
|
|
een planned talks and casual hallway chat. In an unconference\, participan
|
|||
|
|
ts collaboratively set up a schedule for topical conversations. Anyone can
|
|||
|
|
propose a topic. A schedule-board organizes which topics will happen when
|
|||
|
|
and where. Everyone can join (or just listen in on) whichever conversatio
|
|||
|
|
ns they like.\nNever been to one? We'll give a brief overview of the rooms
|
|||
|
|
and times so you can build your schedule.
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/360/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Nurturing the Next Generation of Open Source Contributors
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T140000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T144500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:299@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Tyler Menezes\nMany open source projects are grapplin
|
|||
|
|
g with a crucial issue: finding future contributors and maintainers. This
|
|||
|
|
talk explores the hurdles and solutions in bridging academia and open sour
|
|||
|
|
ce. We discuss what mental barriers students face when it comes to coding
|
|||
|
|
and contributing to open source\, how to craft mentorship resources\, and
|
|||
|
|
what resources projects need to build lasting relationships with students.
|
|||
|
|
LOCATION:329
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/330/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Cooking Up Community: Build the Fire\, Embrace Every Ingredient\,
|
|||
|
|
Always Stir the Pot
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T140000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T144500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:332@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Rick Turoczy\nBuilding a thriving open source communi
|
|||
|
|
ty isn’t just about setting up the right infrastructure — it’s about
|
|||
|
|
lighting the fire\, welcoming every ingredient\, and making sure the pot
|
|||
|
|
stays stirred.\n\nIn this talk\, Rick Turoczy — longtime startup communi
|
|||
|
|
ty builder\, Silicon Florist writer\, and semi-professional stirrer-of-pot
|
|||
|
|
s — shares practical\, heartfelt lessons on how open communities nourish
|
|||
|
|
creativity\, innovation\, and resilience. Drawing inspiration from campfi
|
|||
|
|
res\, communal kitchens\, and a few questionable recipes\, Rick explores w
|
|||
|
|
hat it really takes to keep the flame alive without burning out the chefs.
|
|||
|
|
\n\nTopics include:\n- Building the Fire: Creating the conditions where co
|
|||
|
|
ntributors of all kinds feel warmth\, safety\, and purpose\n- Embracing Ev
|
|||
|
|
ery Ingredient: Recognizing and celebrating every kind of contribution —
|
|||
|
|
code\, documentation\, encouragement\, memes\, and moral support\n- Alway
|
|||
|
|
s Stirring the Pot: Keeping communities dynamic\, curious\, and welcoming
|
|||
|
|
to new flavors and ideas — without letting things get scorched\n\nWhethe
|
|||
|
|
r you're tending a tiny new project or helping stir a massive community st
|
|||
|
|
ew\, you'll leave with a renewed sense of why open source isn't just about
|
|||
|
|
code — it's about collaboration\, nourishment\, and shared possibility.
|
|||
|
|
LOCATION:328
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/298/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:GNU/Linux Loves All
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T140000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T144500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:308@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Timmy James Barnett\nGNU/Linux Loves All is an experi
|
|||
|
|
ence that makes microtonal music accessible through FLO software. Timmy wr
|
|||
|
|
ites FLO software music tools for all people. At this concert\, you will h
|
|||
|
|
ear musical intervals from across millennia on violin\, microtonal guitar\
|
|||
|
|
, and microtonal keyboards\, running through FLO software music tools on G
|
|||
|
|
NU/Linux\, the greatest operating system of all time.
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/318/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Panel: Licenses\, corporations\, community\, and collaboration
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T140000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T144500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:333@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Josh Triplett\nConfirm or deny: Free and open source
|
|||
|
|
software licenses\nshould provide a framework for collaboration between an
|
|||
|
|
y and all\nindividuals and entities interested in working on and using the
|
|||
|
|
covered\ncode\, including hobbyists\, freelancers\, corporations\, and no
|
|||
|
|
nprofit\norganizations. If not true\, what should we do instead? If true\,
|
|||
|
|
how is\nour current set of licenses performing in this area\, especially\
|
|||
|
|
nconsidering wrinkles like SaaS and patents? Furthermore\, we've seen some
|
|||
|
|
\nmodifications published as "additional terms" and as new licenses -- how
|
|||
|
|
\nhave these efforts played out and do we expect to see more of them?\nWe'
|
|||
|
|
ll hear from panelists with expertise in diverse related areas\, and\ninvi
|
|||
|
|
te questions from the audience.
|
|||
|
|
LOCATION:328
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/361/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Is There Really an SBOM Mandate?
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T140000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T144500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:319@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Bradley M. Kuhn\nA consistent mantra of the Software
|
|||
|
|
Bill Of Materials (SBOM) ballyhoo is\nthat various government entities aro
|
|||
|
|
und the world have mandated SBOMs in\nvarious different places. From USA P
|
|||
|
|
OTUS Executive Orders\, to EU Directives\,\nto USA NIST whitepapers — it
|
|||
|
|
's often been repeated that these various\nsources mandate SBOMs as a mand
|
|||
|
|
atory requirement.\n\nLet's look at the source material and find out what
|
|||
|
|
these various orders and\ndirectives actually say\, and figure out what's
|
|||
|
|
really mandated.
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/326/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Unconference
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T140000
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T144500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:376@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:How to get people to care about FOSS\, exploring different sof
|
|||
|
|
tware domains\n\n<a href="https://pad.sfconservancy.org/p/FOSSY25-ROOM-329
|
|||
|
|
">Pad link</a>
|
|||
|
|
LOCATION:329
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Talk
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T140000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T144500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:315@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:333
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Unconference
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T140000
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T144500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:366@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:AI issues - safety\, licensing\, etc.\n\n<a href="https://pad.
|
|||
|
|
sfconservancy.org/p/FOSSY25-ROOM-328">Pad link</a>
|
|||
|
|
LOCATION:328
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:An Adventure in Data Modeling
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T140000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T144500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:310@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Mark Wong\nThis is a tale about one company's experie
|
|||
|
|
nce with a database schema design refactor to use the Entity-Attribute-Val
|
|||
|
|
ue (EAV) data model on its members. I will describe the original data mode
|
|||
|
|
l and why there was a need to move to a new data model\, which the EAV was
|
|||
|
|
chosen for. This decision was made without realizing that the EAV data m
|
|||
|
|
odel is considered an anti-pattern for relational data modeling. There wa
|
|||
|
|
s some stumbling along the way but the company recovered and succeeded in
|
|||
|
|
implementing the EAV data model with some on-the-fly data transformation.
|
|||
|
|
The moral of the story really is to not use the EAV data model\, but chan
|
|||
|
|
ging the data models is not always trivial. Hopefully this story can sti
|
|||
|
|
ll help make the EAV data model bearable for the short term.
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/363/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Unconference
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T140000
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T144500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:362@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Whats next for academic Open Source and OSPO / Semantics in Ma
|
|||
|
|
chine Learning Objective Functions\n\n<a href="https://pad.sfconservancy.o
|
|||
|
|
rg/p/FOSSY25-ROOM-338">Pad link</a>
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Setting Up A Simple XMPP Server
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T140000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T144500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:355@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Root\nThis talk will showcase the simplicity and ease
|
|||
|
|
of setting up your own XMPP server using the Snikket software\, walking s
|
|||
|
|
tep-by-step through the process using slides. The end result will be a ful
|
|||
|
|
ly functioning XMPP server that can be used throughout the remainder of th
|
|||
|
|
e conference between all attendees. There will be a demonstration of the f
|
|||
|
|
eatures available to a Snikket Instance including\, but not limited to\, i
|
|||
|
|
nviting others to join your server\, group chats that are private or publi
|
|||
|
|
c\, adding contacts\, managing and updating the instance as the admin\, cr
|
|||
|
|
eating limited accounts for kids\, and steps for more secure end-to-end en
|
|||
|
|
cryption. This talk will also dive into some personal privacy\, security\,
|
|||
|
|
and persona considerations and how they will be affected by your threat m
|
|||
|
|
odel.
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/286/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Talk
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T140000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T144500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:287@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Riding Subiquity With No Handlebars
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T140000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T144500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:277@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Romeo S\nCanonical\, never happy with existing standa
|
|||
|
|
rds\, wrote their own auto-installer just for Ubuntu. It has some "fun" us
|
|||
|
|
age\, which we will cover in great detail. After this talk\, you will be a
|
|||
|
|
ble to install Ubuntu Server with your hands tied behind your back\, wheth
|
|||
|
|
er it be on a virtual machine or bare metal\, with or without a network co
|
|||
|
|
nnection\, in a datacenter or in your lap. We will also have some fun talk
|
|||
|
|
ing about the perplexing decisions that Canonical makes and some of the lo
|
|||
|
|
ng-standing bugs in Subiquity\, along with workarounds.
|
|||
|
|
LOCATION:329
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/305/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Popping kernels for Linux distributions
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T140000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T144500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:240@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Neal Gompa\nPackagers in Linux distributions do a lot
|
|||
|
|
to ensure the software you use is up to date\, integrated in the platform
|
|||
|
|
\, and most importantly: works! But one package stands out among the other
|
|||
|
|
s in importance: the Linux kernel. Over the past few years\, I've become a
|
|||
|
|
Linux kernel package maintainer for a couple of Linux distributions (nota
|
|||
|
|
bly Fedora Asahi Remix and CentOS Stream Hyperscale). This talk will share
|
|||
|
|
my experiences in becoming and being a Linux kernel package maintainer: t
|
|||
|
|
he good\, the bad\, and the sometimes ugly.\n\nThis will be centered aroun
|
|||
|
|
d two very distinct types of kernel packages: one where the kernel is most
|
|||
|
|
ly upstream and low patching (CentOS Stream Hyperscale) and one where the
|
|||
|
|
kernel has a significant downstream patch load (Fedora Asahi Remix). The c
|
|||
|
|
ompare and contrast will demonstrate why Linux distributions make the choi
|
|||
|
|
ces they do around package maintenance and concretely show why philosophie
|
|||
|
|
s like "upstream first" and similar matter.
|
|||
|
|
LOCATION:328
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/299/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Unconference
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T140000
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T144500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:342@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Setting goals and spending money / Meta-crisis / Coordination
|
|||
|
|
problem\n\n<a href="https://pad.sfconservancy.org/p/FOSSY25-ROOM-327">Pad
|
|||
|
|
link</a>
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Open source your repository: a roadmap
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T140000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T144500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:293@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Mike Jang\nThis is open source done right. Open sourc
|
|||
|
|
ing existing software is more than just "pushing a button\," It involves s
|
|||
|
|
erious preparation\, including:\n\n- Choosing reasons to go open source\n-
|
|||
|
|
Auditing security\n- Scrubbing PII\n- Lawyers and the license\n- Deciding
|
|||
|
|
what to do about commits\n- Setting ground rules for contributors\n- Shar
|
|||
|
|
ing with your community\n- Follow-up hackathons\n\nWhen people look at ope
|
|||
|
|
n source software\, they first look at documentation. When open source dev
|
|||
|
|
elopers find a promising project\, they expect to get involved. One part o
|
|||
|
|
f the process is with open source software.\n\nAttendees will come out of
|
|||
|
|
this session with:\n\n- Access to a template repository\n- A checklist to
|
|||
|
|
follow\, which addresses legal\, security\, and community requirements\n-
|
|||
|
|
An understanding of the work required to move to open source\n- Tips for h
|
|||
|
|
ackathons\, based on real-world experience with open source newbies\n\nInt
|
|||
|
|
ernally\, we overcame barriers before we could "push the button." External
|
|||
|
|
ly\, we helped open source newbies make substantive contributions\, well b
|
|||
|
|
eyond the "typo fix."\n\nOver the past few days\, we've experienced the va
|
|||
|
|
riety of issues that can come from a hackathon\, especially with Git newbi
|
|||
|
|
es. However\, we've found that encouraging new Git users increases the qua
|
|||
|
|
lity of contributions based on the diversity of experiences.
|
|||
|
|
LOCATION:333
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/341/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Unconference
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T140000
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T144500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:371@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Music and video games\n\n<a href="https://pad.sfconservancy.or
|
|||
|
|
g/p/FOSSY25-ROOM-333">Pad link</a>
|
|||
|
|
LOCATION:333
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Lessons from a Decade of Open Source Sustainability Research
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T140000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T144500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:349@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Igor Steinmacher\nSeveral FOSS projects struggle with
|
|||
|
|
long-term sustainability. This talk walks through years of research and d
|
|||
|
|
evelopment focused on addressing some of the most pressing challenges face
|
|||
|
|
d related to the sustainability of FOSS communities: newcomer onboarding\,
|
|||
|
|
maintainer burnout\, and project governance. I will begin by discussing i
|
|||
|
|
nterventions to support newcomers' onboarding\, including community-driven
|
|||
|
|
mentorship strategies\, structured contribution paths\, and other approac
|
|||
|
|
hes\, designed to build confidence and skills early in the contribution pr
|
|||
|
|
ocess. I will also present ongoing work exploring how Large Language Model
|
|||
|
|
s (LLMs) can be used to create conversational agents that assist contribut
|
|||
|
|
ors and reduce repetitive questions directed at maintainers\, helping scal
|
|||
|
|
e mentoring while keeping community standards. I will also share insights
|
|||
|
|
from longitudinal analyses of developer activity and engagement patterns\,
|
|||
|
|
including the role of personal and project-level breaks in sustaining hea
|
|||
|
|
lthy contribution cycles and how we may use this to plan. Throughout the t
|
|||
|
|
alk\, I will reflect on how these align with broader structural improvemen
|
|||
|
|
ts. In one example\, a governance shift in the data.table project was acco
|
|||
|
|
mpanied by investments in multilingual documentation and structured issue
|
|||
|
|
triage---steps that revitalized participation and distributed responsibili
|
|||
|
|
ty. Together\, these threads present a holistic vision for building more s
|
|||
|
|
ustainable\, inclusive\, and resilient FOSS communities\, combining techni
|
|||
|
|
cal scaffolding\, community design\, and human-centered practices.
|
|||
|
|
LOCATION:333
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/343/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Talk
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T140000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T144500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:281@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Where Open Research Meets Open Source: The OSF as a Gateway to Aca
|
|||
|
|
demic Collaboration
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T140000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T144500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:339@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Daniel Steger\nThe Open Science Framework (OSF)\, dev
|
|||
|
|
eloped and maintained by the Center for Open Science (COS) is a free\, ope
|
|||
|
|
n-source platform that helps researchers around the world manage and share
|
|||
|
|
their work openly and transparently. With more than 800\,000 users across
|
|||
|
|
disciplines and continents\, the OSF supports a global community of schol
|
|||
|
|
ars seeking reproducibility and openness in scholarship. But the OSF is al
|
|||
|
|
so something more: a unique open-source ecosystem built to bridge the gap
|
|||
|
|
between research needs and technical contributions.\n\nIn this session\, w
|
|||
|
|
e’ll explore how OSF offers a low-barrier entry point for students\, edu
|
|||
|
|
cators\, and developers who want to make a meaningful impact on the resear
|
|||
|
|
ch world. Through its modular architecture and integration of microservice
|
|||
|
|
s\, the OSF enables contributors to build tools that directly improve how
|
|||
|
|
science is done\, supporting workflows from study planning through to publ
|
|||
|
|
ication and sharing of any resource type. \n\nBeyond technical infrastruct
|
|||
|
|
ure\, OSF fosters a “social open” environment that welcomes and suppor
|
|||
|
|
ts new contributors. We offer active community spaces like our Discord ser
|
|||
|
|
ver\, regular onboarding events\, transparent project boards on GitHub\, a
|
|||
|
|
nd continually updated documentation and guides. We also collaborate acros
|
|||
|
|
s open-source communities to stay aligned with shared values and best prac
|
|||
|
|
tices in open development.\n\nAttendees of this presentation will learn an
|
|||
|
|
d experience:\n-Highlighting the OSF as a free\, open platform that lowers
|
|||
|
|
the barrier for sharing scholarly and educational materials for researche
|
|||
|
|
rs around the world\n- Showcasing opportunities for researchers and educat
|
|||
|
|
ors as both end-users and code\, feedback\, and feature contributors throu
|
|||
|
|
gh the OSF open source community “help wanted board\,” showing tasks r
|
|||
|
|
eady for all levels of developers. \n- Spotlighting our new open-source in
|
|||
|
|
tegration ecosystem as a low-friction entry point for technical contributo
|
|||
|
|
rs in academic settings that brings new users and expanded capabilities fo
|
|||
|
|
r OSF and integrated tools and services\n- Provide real-time opportunities
|
|||
|
|
for participants to grow their FOSS engagement through an interactive fee
|
|||
|
|
dback and co-design activity\n- Examples of institutional collaborations a
|
|||
|
|
nd feature feedback loops directly from OSF researchers and educators\n- D
|
|||
|
|
emonstrate how the OSF builds and supports an open-source community commit
|
|||
|
|
ted to reproducibility and access of academic research. \n\nGetting involv
|
|||
|
|
ed is easy and impactful. Whether you're a small developer group\, a class
|
|||
|
|
room exploring real-world FOSS engagement\, or an individual contributor\,
|
|||
|
|
there are many ways to plug into our community. We’re always looking fo
|
|||
|
|
r collaborators\, especially those excited about making tools that amplify
|
|||
|
|
open science around the world. Whether you're a dev team exploring ways t
|
|||
|
|
o contribute to the future of knowledge sharing\, an educator guiding stud
|
|||
|
|
ents through real-world projects\, or simply someone passionate about buil
|
|||
|
|
ding for impact\, the OSF community welcomes your contribution—and your
|
|||
|
|
curiosity.
|
|||
|
|
LOCATION:329
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/338/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Break
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T144500
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T150000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:244@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Break
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T144500
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T150000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:246@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Break
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T144500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T150000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:245@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Break
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T144500
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T150000
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:247@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Unconference
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T150000
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T154500
|
|||
|
|
DTSTAMP:20260223T173350Z
|
|||
|
|
UID:346@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Names are hard! What is a better word than "upstream" for dist
|
|||
|
|
ros? / What it takes to build strong teams / Building better collaborators
|
|||
|
|
\n\n<a href="https://pad.sfconservancy.org/p/FOSSY25-ROOM-327">Pad link</a
|
|||
|
|
>
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:HAX Lab: FOSS community becomes the classroom
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T150000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T154500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:340@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Bryan T Ollendyke\nThis talk is a case study in how f
|
|||
|
|
using open source contribution with classroom teaching can directly lead t
|
|||
|
|
o increases in contributors and improved developer experience! DX often co
|
|||
|
|
mes down to new users being able to figure out your software and students
|
|||
|
|
learning new technologies provide a great basis for building around.\n\nHA
|
|||
|
|
X Lab is a collaboration between multiple colleges at Penn State. Informat
|
|||
|
|
ion Sciences and Technology crossed with Arts and Architecture\, has provi
|
|||
|
|
ded a playground to grow and sustain open source in a unique way I'd love
|
|||
|
|
to share. Now there is an IST course (256) that teaches students modern we
|
|||
|
|
b development through direct and indirect contribution to the platform\, H
|
|||
|
|
AX Lab\, HAX The Club\, and collaborations across clubs directly and indir
|
|||
|
|
ectly improving the ecosystem! You can learn more about the Student Innova
|
|||
|
|
tion Pipeline here: https://haxtheweb.org/hax-lab/student-innovation-pipel
|
|||
|
|
ine\n\nDirect contribution:\n- Labs solve entry level problems in the ecos
|
|||
|
|
ystem\n- Course capstone projects help contribute to larger needs in the c
|
|||
|
|
ommunity\n- HAX Lab allows students to go further via internships and inde
|
|||
|
|
pendent studies\n- a student driven HAX Club allows them to take their kno
|
|||
|
|
wledge to application in the larger university community\n\nIndirect:\n- S
|
|||
|
|
tudents use the HAX cli in order to learn about modern web tooling. This p
|
|||
|
|
rovides DX feedback to our community\n- Students often keep contributing a
|
|||
|
|
fterwards by creating sites on the platform\n- Several students have conti
|
|||
|
|
nued to contribute in the years after the course\n- Other groups internall
|
|||
|
|
y are writing HAX into grants and building business plans that incorporate
|
|||
|
|
HAX unique capabilities\n\nWhat you'll learn:\n- How our pipeline works\n
|
|||
|
|
- Contribution timelines\, scale\, and quality of contributions\n- Example
|
|||
|
|
s of additional ways to engage student communities to increase contributio
|
|||
|
|
ns\n- How you can get involved with HAX and use it in your community\n\nMo
|
|||
|
|
re about HAX:\nHAX is short for Headless Authoring eXperience\, it is a we
|
|||
|
|
b based ecosystem that makes it easier to build websites and then provides
|
|||
|
|
website-tonight style click and build software that you can take with you
|
|||
|
|
\, download\, and remix easily. It was an idea and approach to make it eas
|
|||
|
|
ier to develop web content online.
|
|||
|
|
LOCATION:329
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/333/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Panel: Ongoing Things in the Kernel Community
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T150000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T154500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:248@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Darrick J. Wong\n- Kernel integration with mainline\n
|
|||
|
|
- Upstreaming stuff from AsahiLinux\n- Containerizing filesystems\n- Awful
|
|||
|
|
ness of vendor kernels\n- Adding Rust\n\nThere will also be room for audie
|
|||
|
|
nce questions.
|
|||
|
|
LOCATION:328
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/359/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Databases and Diversity
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T150000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T152000
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:288@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Stacey Haysler\nWhile we have great diversity in data
|
|||
|
|
bases—from open source systems such as PostgreSQL and CouchDB\, to propr
|
|||
|
|
ietary and heavily licensed ones such as Oracle— human diversity in the
|
|||
|
|
database community is not nearly equivalent. Diversity (and lack thereof)
|
|||
|
|
in the technical community has been a topic of increasing discussion the
|
|||
|
|
past few years. While we have made some progress—even submitting a propo
|
|||
|
|
sal for a talk on diversity to a conference is a significant change—we h
|
|||
|
|
ave some distance to travel still. While won't get there in 25 minutes\, w
|
|||
|
|
e will cover a fair amount of ground!\n\nWe will review current efforts in
|
|||
|
|
the technical community to improve diversity\, as well as ideas that have
|
|||
|
|
been discussed and need someone to develop them. \n\nYou will also learn
|
|||
|
|
what you\, as one individual\, can do in your daily life to improve the di
|
|||
|
|
versity of our community.
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/292/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Glue Work Makes the Community Work: Sustaining OSS Through Invisib
|
|||
|
|
le Labor
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T150000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T154500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:350@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Zixuan Steve Feng\nThe success of any OSS team projec
|
|||
|
|
t\, be it OSS or proprietary\, depends on glue work to bind the project an
|
|||
|
|
d its people together. Glue work\, such as writing maintenance code\, upda
|
|||
|
|
ting documentation\, and responding to user queries\, is crucial but is of
|
|||
|
|
ten invisible\, unglamorous\, and underappreciated. There is no guidance o
|
|||
|
|
n how to characterize glue work in OSS and understand its influence on con
|
|||
|
|
tributor experiences. OSS communities remain uncertain about what to contr
|
|||
|
|
ibute\, what to acknowledge\, how to gauge the impact of glue work\, and w
|
|||
|
|
hy these efforts deserve equitable appreciation.\n\nOver the past year\, o
|
|||
|
|
ur cross-disciplinary team from Google\, Microsoft\, CNCF\, and Oregon Sta
|
|||
|
|
te University engaged 300+ OSS practitioners via focus group discussions\,
|
|||
|
|
interviews\, and surveys. We systematically investigated glue work in OSS
|
|||
|
|
\, examining what it is\, the comprehensive forms it takes\, where it occu
|
|||
|
|
rs\, how contributors can get involved\, how it can be recognized and ackn
|
|||
|
|
owledged\, and its critical impact on contributor experiences and the long
|
|||
|
|
-term sustainability of OSS communities. \n\nWe are here to provide action
|
|||
|
|
able strategies through practical taxonomies that help OSS communities cat
|
|||
|
|
egorize\, trace\, and acknowledge these often invisible efforts\, as well
|
|||
|
|
as to raise awareness of glue work and lower the barriers for more people
|
|||
|
|
to contribute to OSS. We aim to actively shift the Open Source narrative t
|
|||
|
|
o recognize and value these contributions\, fostering a more inclusive and
|
|||
|
|
holistic view of community participation. We are initiating a dedicated G
|
|||
|
|
lue Work OSS community to encourage individuals at all levels of coding ex
|
|||
|
|
perience to step forward\, contribute\, and acknowledge the myriad ways in
|
|||
|
|
which everyone can make a significant impact. Learn more https://gluewor
|
|||
|
|
k.netlify.app/.
|
|||
|
|
LOCATION:333
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/352/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Unconference
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T150000
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T154500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:363@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Threats to the Open Web / What do we do if or when Firefox dis
|
|||
|
|
appears? / Observability is Broken\n\n<a href="https://pad.sfconservancy.o
|
|||
|
|
rg/p/FOSSY25-ROOM-338">Pad link</a>
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Open
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T150000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T152000
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:391@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:329
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:The Kalpa Desktop\, A Desktop for people that just want to get thi
|
|||
|
|
ngs done.
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T150000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T154500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:278@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Shawn W Dunn\nKalpa Desktop is a Plasma desktop deriv
|
|||
|
|
ed from MicroOS\, and Tumbleweed\, providing a immutable system base\, wit
|
|||
|
|
h a containerized workflow\, through distrobox and podman\, and Desktop ap
|
|||
|
|
plications via Flathub.\n\nKalpa grew out of the initial work by Richard B
|
|||
|
|
rown\, with MicroOS Desktop\, but has diverged over the past three years.\
|
|||
|
|
n\nKalpa's focus is on providing users with:\n- A well-tested and current
|
|||
|
|
Plasma-Wayland desktop\n- A minimal installation\, without a bunch of appl
|
|||
|
|
ications you may not want or need\n- Robust stability\, through the use of
|
|||
|
|
atomic updates\, no more broken updates\n- Just a "Damn Good™" basic de
|
|||
|
|
sktop installation\, that's designed to *be* a desktop\, and that's all\n\
|
|||
|
|
nThis presentation will present the current state of the Project\, and exa
|
|||
|
|
mine the future roadmap for Kalpa Desktop.
|
|||
|
|
LOCATION:329
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/306/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Talk
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T150000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T154500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:334@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:328
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Talk
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T150000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T154500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:282@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Telecomms for Preppers
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T150000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T152500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:356@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Phillip\nSoftware in general\, and telecommunication
|
|||
|
|
in particular\, relies on a sprawling infrastructure of networking\, hosti
|
|||
|
|
ng\, and electrical infrastructure that no single person understand. On th
|
|||
|
|
e other hand\, a key component of mutual aid and disaster preparedness is
|
|||
|
|
the knowledge and tools to provide such services in a context where your i
|
|||
|
|
mmediate community might have to provide some of its own needs. Let's talk
|
|||
|
|
about how you could contribute to that by building communication software
|
|||
|
|
that you can use\, modify\, and fix on your own as much as possible.
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/287/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Making Esoteric Beauty Accessible: Befunge in 2025
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T150000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T152500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:311@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Robin Brown\nBefunge is a 2-dimensional esoteric prog
|
|||
|
|
ramming language that is stack-based with an emphasis on code being able t
|
|||
|
|
o modify itself at runtime. It was designed to be hard to compile and ente
|
|||
|
|
rtaining. While even the most well-written Befunge looks obfuscated\, with
|
|||
|
|
the right tools we can visualize and make accessible its concepts and str
|
|||
|
|
ange beauty. Join Robin Brown as she teaches the basics of Befunge using n
|
|||
|
|
ew interactive tools and talks briefly about its past and future.
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/316/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Unconference
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T150000
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T154500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:367@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Eleminating CLAs / Right to Repair\n\n<a href="https://pad.sfc
|
|||
|
|
onservancy.org/p/FOSSY25-ROOM-328">Pad link</a>
|
|||
|
|
LOCATION:328
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Making waterfalls in Godot
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T150000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T154500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:320@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Tom Lechner\nCome learn about some ways to display wa
|
|||
|
|
terfalls in the open source Godot game engine! Video game fluid flow is a
|
|||
|
|
complex subject\, and this talk will outline various methods to cheat so t
|
|||
|
|
hat you don't really have to know complex math to make something acceptabl
|
|||
|
|
e. Inspired by a variety of waterfalls in the Pacific Northwest of the USA
|
|||
|
|
\, this talk will discuss custom tooling to generate waterfalls in Godot\,
|
|||
|
|
based on how water would fall down digital terrain\, and how to use other
|
|||
|
|
open source software for art such as Blender\, Krita\, Gimp to polish dif
|
|||
|
|
ferent parts of the scenery.
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/353/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Unconference
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T150000
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T154500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:377@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Mesh Networking / How you got started in FOSS\n\n<a href="http
|
|||
|
|
s://pad.sfconservancy.org/p/FOSSY25-ROOM-329">Pad link</a>
|
|||
|
|
LOCATION:329
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Designing for Collaboration: A Toolkit for Open and Inclusive Envi
|
|||
|
|
ronmental Research
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T150000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T152000
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:393@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Cathy Richards\nAs communities worldwide confront urg
|
|||
|
|
ent environmental challenges\, open source technologies and data infrastru
|
|||
|
|
ctures are increasingly central to how we understand\, protect\, and susta
|
|||
|
|
in our environments. Yet\, persistent gaps remain between the development
|
|||
|
|
of open tools\, academic research\, and the practical needs of the communi
|
|||
|
|
ties most affected by environmental issues.\n\nOpen Environmental Data Pro
|
|||
|
|
ject (OEDP) and partners are addressing this gap through the creation of t
|
|||
|
|
he Digital Toolkit for Collaborative Environmental Research. This toolkit\
|
|||
|
|
, grounded in research conducted in 2024\, provides actionable resources f
|
|||
|
|
or open source developers\, socio-environmental researchers\, and communit
|
|||
|
|
y organizations seeking to build and maintain effective\, community-driven
|
|||
|
|
collaborations. By employing a design pattern language approach\, the too
|
|||
|
|
lkit offers concrete solutions and strategies organized around key themes
|
|||
|
|
such as building trust through transparent data practices\, navigating pow
|
|||
|
|
er dynamics in collaborations\, and fostering sustainable models of commun
|
|||
|
|
ity data stewardship. The toolkit emphasizes the FOSS values of openness a
|
|||
|
|
nd transparency by encouraging open access to data and documentation\; it
|
|||
|
|
supports collaboration and inclusivity through community-driven decision-m
|
|||
|
|
aking processes\; and it advances sustainability by promoting reusable\, a
|
|||
|
|
daptable tools that empower all participants to contribute and benefit equ
|
|||
|
|
itably.\n\nThis talk will share lessons learned from OEDP’s work\, highl
|
|||
|
|
ighting how the toolkit translates open infrastructure into inclusive\, pr
|
|||
|
|
actical frameworks that empower communities to use data for local action a
|
|||
|
|
nd advocacy. Attendees will gain insights into how research can inform the
|
|||
|
|
design of open source tools that truly serve community needs\, and how pr
|
|||
|
|
actitioners and researchers can collaborate more effectively to bridge the
|
|||
|
|
gap between theory and practice. The session will also explore the broade
|
|||
|
|
r implications for FOSS communities\, focusing on how participatory approa
|
|||
|
|
ches to tool development and data governance can drive more equitable and
|
|||
|
|
sustainable outcomes in environmental contexts.
|
|||
|
|
LOCATION:333
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/346/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Talk
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T150000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T154500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:316@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:333
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Unconference
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T150000
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T154500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:372@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Advances in RSS / Translating C to Rust\n\n<a href="https://pa
|
|||
|
|
d.sfconservancy.org/p/FOSSY25-ROOM-333">Pad link</a>
|
|||
|
|
LOCATION:333
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Open
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T150000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T152000
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:388@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:328
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Making P2P apps with Spritely Goblins
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T150000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T152000
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:395@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Diana Belle\nThe Spritely Institute has been working
|
|||
|
|
hard on a distributed systems programming library called Goblins\, whose c
|
|||
|
|
leverness simplifies all the difficult parts of getting multiplayer code r
|
|||
|
|
ight. How different is a multiplayer game from a peer-to-peer app\, really
|
|||
|
|
? Let's dive in and I'll show you how to get involved with this emerging t
|
|||
|
|
echnology\, whether in Scheme\, or JavaScript!
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/313/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Open
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T152500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T154500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:392@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:329
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:How to Hold It Together When It All Falls Apart: Surviving a Toxic
|
|||
|
|
Open Source Project Without Losin
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T152500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T154500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:396@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Cami Kaos\nI love open source. I always have. I’ve
|
|||
|
|
spent more than a decade building\, managing\, and advocating for open sou
|
|||
|
|
rce communities—through mentorship\, moderation\, DEIB strategy\, suppor
|
|||
|
|
t tickets\, and everything in between. It’s been one of the great loves
|
|||
|
|
of my career. But at some point\, I found myself in a project where the op
|
|||
|
|
enness was performative\, the source of truth was... well\, interpretive\,
|
|||
|
|
and the community slowly\, quietly\, turned toxic.\n\nThis talk isn’t a
|
|||
|
|
revenge arc or a cautionary tale told with pitchforks. It’s a survival
|
|||
|
|
guide—and a personal one. Inspired in part by Pema Chödrön’s When Th
|
|||
|
|
ings Fall Apart\, it’s about finding groundlessness in a place that once
|
|||
|
|
felt solid\, and learning how to stay present and compassionate even when
|
|||
|
|
the community you helped build begins to crumble around you.\n\nWe’ll e
|
|||
|
|
xplore:\n\nThe subtle warning signs of a community in distress\n\nWhat “
|
|||
|
|
toxic” actually looks like in open source (hint: it’s often quiet and
|
|||
|
|
polite)\n\nThe emotional labor of community leadership\, especially when y
|
|||
|
|
ou’re the one holding everything together\n\nHow to create space for you
|
|||
|
|
r own wellbeing while still honoring your values\n\nAnd\, yes—how to beg
|
|||
|
|
in again. How to grieve a project\, rediscover joy\, and fall back in love
|
|||
|
|
with open source\, on your terms.\n\nIf you've ever asked yourself\, “I
|
|||
|
|
s it me? Or is this project slowly draining the life out of me?”—this
|
|||
|
|
talk is for you. Spoiler: It’s not just you. Let’s talk about what hap
|
|||
|
|
pens when things fall apart—and how we hold it together anyway.
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/323/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Open
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T152500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T154500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:390@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:328
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:BlueHats: Public servant advocates for software freedom
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T152500
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T154500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:383@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Michael Downey\nBlueHats is a worldwide community of
|
|||
|
|
public servants (teachers\, researchers and other government workers\, etc
|
|||
|
|
.) who promote FOSS use in\, by\, and for the public sector. BlueHats beli
|
|||
|
|
eve that tax money spent on software development should result in Free Sof
|
|||
|
|
tware\, and they support the principle of "public money\, public code". A
|
|||
|
|
ll public servants around the world are invited to join this movement\, so
|
|||
|
|
come and learn more about the movement and help us spread the word!
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/319/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:From Campus to Network: Creating the UC System-Wide OSPO Initiativ
|
|||
|
|
e
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T152500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T154500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:394@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Laura Langdon\nLaura Langdon from the UC OSPO Network
|
|||
|
|
will share lessons learned from the early stages of building a network of
|
|||
|
|
academic OSPOs across the UC system. Representing the team that supports
|
|||
|
|
the six campuses in the UC OSPO Network\, she will discuss both benefits a
|
|||
|
|
nd challenges encountered while developing this first-of-its-kind system-w
|
|||
|
|
ide network. She will explore how her experiences with the network's three
|
|||
|
|
core working groups—sustainability of open source development\, discove
|
|||
|
|
ry of open source work in research\, and education in fostering open sourc
|
|||
|
|
e skills—have shaped her understanding of successful OSPO networks. Laur
|
|||
|
|
a will focus on building community connections and establishing pathways f
|
|||
|
|
or collaboration between institutions. Drawing from her first-hand experie
|
|||
|
|
nce\, Laura will provide practical insights for others looking to establis
|
|||
|
|
h OSPO networks in their institutions.
|
|||
|
|
LOCATION:333
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/344/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Messaging interoperability with MLS\, MIMI and XMPP
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T152500
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T154500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:384@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Marvin W.\nXMPP was and still is the major open stand
|
|||
|
|
ard for federated instant messaging\, originally designed to allow bridgin
|
|||
|
|
g between existing networks.\n\nIn recent years\, due to ongoing regulator
|
|||
|
|
y efforts\, a new attempt at interoperability between instant messengers\,
|
|||
|
|
MIMI (More Instant Messaging Interoperability)\, was started at the IETF\
|
|||
|
|
, the internet protocol standardization body. Based on the latest and grea
|
|||
|
|
test end-to-end-encryption standard MLS (Messaging Layer Security) it's me
|
|||
|
|
ant to partially provide what XMPP failed to deliver. This talk will give
|
|||
|
|
an overview on the topics of MLS and MIMI and how it can play together wit
|
|||
|
|
h XMPP.
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/288/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Talk
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T152500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T154500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:381@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Coffee/tea break
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T154500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T163000
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:385@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Coffee\, tea\, and snack break
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Coffee/tea break
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T154500
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T163000
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:235@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Coffee\, tea\, and snack break
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Coffee/tea break
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T154500
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T163000
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:238@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Coffee\, tea\, and snack break
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Coffee/tea break
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T154500
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T163000
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:237@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Coffee\, tea\, and snack break
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Unconference
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T163000
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T171500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:359@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Decentralization\n\n<a href="https://pad.sfconservancy.org/p/F
|
|||
|
|
OSSY25-ROOM-338">Pad link</a>
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Adventures in Onboarding: Helping New Users Navigate Federated Ser
|
|||
|
|
vices
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T163000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T171500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:357@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Gideon Mayhak\nTales from the front lines of supporti
|
|||
|
|
ng new users of federated services! We've all been there: you're excited
|
|||
|
|
about a new technology and you want to tell your friends. You've already
|
|||
|
|
gotten into the weeds and you come on a bit too strong. Does your friend
|
|||
|
|
need to know what "XMPP” stands for? Does it matter if they know what a
|
|||
|
|
domain is?\n\nThis talk will be a review of common stumbling blocks for n
|
|||
|
|
ew users\, tips on keeping things simple with your friends and family\, an
|
|||
|
|
d a discussion about how to help people grow into their newfound communiti
|
|||
|
|
es. We’ll also take a closer look at demystifying common terms in the w
|
|||
|
|
orld of XMPP so you’re ready to answer some of the tougher questions in
|
|||
|
|
life\, like\, “What is a Snikket?”\n\nCome learn more about open feder
|
|||
|
|
ated systems and how you can help others join in on the fun!
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/285/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:The Cathedral and the Bizarre\, or Dual-Booting for Fun and Prophe
|
|||
|
|
t: Using Linux to Enhance TempleOS
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T163000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T171500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:312@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Toby Betts\nDual-booting is a useful method to run tw
|
|||
|
|
o operating systems on the same machine. Different OSes might help you har
|
|||
|
|
ness the full potential of your hardware\, or it may be necessary because
|
|||
|
|
of software limitations. It lets you tailor your computing experience to y
|
|||
|
|
our own unique needs. Yet few people run different operating systems from
|
|||
|
|
the same disk partition\, where both OSes coexist in the same place in the
|
|||
|
|
same file system. This talk will outline the steps to combine Linux with
|
|||
|
|
another open source OS known as TempleOS in a very small amount of disk sp
|
|||
|
|
ace\, and how blending them together can create a unique and fun programmi
|
|||
|
|
ng experience.
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/324/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Unconference
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T163000
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T171500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:373@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:FOSS Graphic Design / Rust Firmware Emedded\n\n<a href="https:
|
|||
|
|
//pad.sfconservancy.org/p/FOSSY25-ROOM-333">Pad link</a>
|
|||
|
|
LOCATION:333
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:I Didn't Know Postgres Could Do That!
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T163000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T171500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:313@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Robert Treat\nPostgreSQL is often thought of as "The
|
|||
|
|
Database for DBAs"\, but what more\nand more developers are finding out is
|
|||
|
|
that what makes Postgres "The\nWorlds Most Advanced Open Source Database"
|
|||
|
|
is its wide array of\nfeatures\, many of which are really geared towards
|
|||
|
|
users who want to\nbuild applications on top of Postgres.\n\nIn this talk\
|
|||
|
|
, we'll look at some of the features in Postgres you may not\nhave seen in
|
|||
|
|
other database systems\, and talk about how you can make use\nof those fe
|
|||
|
|
atures in your applications. Queries\, indexing\, data types\,\nand more w
|
|||
|
|
ill all be up for discussion as we show you examples of just\nwhat Postgre
|
|||
|
|
s can do.
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/366/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Talk
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T163000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T171500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:301@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:329
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Unconference
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T163000
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T171500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:343@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Effects of Political Polarization on FOSS Communitites / Gover
|
|||
|
|
nance\, Cooperatives\, etc.\n\n<a href="https://pad.sfconservancy.org/p/FO
|
|||
|
|
SSY25-ROOM-327">Pad link</a>
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:A Hyperscaler’s operating system strategy: working with CentOS a
|
|||
|
|
nd Fedora
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T163000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T171500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:279@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Michel Lind\nWhen an organization's Linux deployment
|
|||
|
|
gets large enough\, a curious emergent property appears - the incentives s
|
|||
|
|
tart to favor developing in-house Linux expertise\, as opposed to outsourc
|
|||
|
|
ing operating systems support to external vendors.\n\nAt the same time\, g
|
|||
|
|
iven the scale involved\, such organizations tend to prefer having a stabl
|
|||
|
|
e base to build on - thus the appeal of slower-moving enterprise distribut
|
|||
|
|
ions\, except with in-house customizations on top.\n\nIn this talk we are
|
|||
|
|
going to discuss some of the choices we made at Meta for our Linux fleet\,
|
|||
|
|
and the thought process behind that. We hope that organizations in a simi
|
|||
|
|
lar situation can benefit from our experience\, and that community members
|
|||
|
|
whose interests are aligned can benefit from our contributions and consid
|
|||
|
|
er participating in the community projects we are involved in.
|
|||
|
|
LOCATION:329
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/308/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Talk
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T163000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T171500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:317@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:333
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Mobile Gaming with FOSS
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T163000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T171500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:283@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Edward Ly\nMobile gaming is an industry that is rapid
|
|||
|
|
ly growing to the point where it is now more popular (and profitable) than
|
|||
|
|
PC and console gaming combined. Yet\, much of the well-known efforts to s
|
|||
|
|
upport gaming on Linux (e.g. emulators\, compatibility layers\, gaming-foc
|
|||
|
|
used distributions) remains within the PC and console gaming spaces. This
|
|||
|
|
talk will briefly explain the state of mobile gaming today\, as well as wh
|
|||
|
|
y and how FOSS game development should expand into the mobile sector. Whet
|
|||
|
|
her you are a gamer or a developer (no matter your skill level)\, come joi
|
|||
|
|
n us to learn about the best mobile games you haven't heard yet or even ho
|
|||
|
|
w to get started developing one yourself!
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/311/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:The Subtle Art of Lying with Statistics
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T163000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T171500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:321@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Dave McAllister\n"Lies\, damned lies and statistics."
|
|||
|
|
While true\, only statistics allow you to lie to yourself.\n\nLet's explo
|
|||
|
|
re how statistics can sometimes trick us into believing something untrue.
|
|||
|
|
This isn't always done intentionally\; we mislead ourselves without realiz
|
|||
|
|
ing it. We'll look at how focusing solely on recent events\, choosing spec
|
|||
|
|
ific data to look at\, and making assumptions about the size of a group ca
|
|||
|
|
n lead us to the wrong conclusions. We'll show examples of how graphs and
|
|||
|
|
numbers can be used in misleading ways. The presentation aims to teach you
|
|||
|
|
to look at statistics more critically\, understand their limits\, and avo
|
|||
|
|
id fooling yourself with numbers.
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/314/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:A Multi-Campus Survey of Open Source Contributors at the Universit
|
|||
|
|
y of California
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T163000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T171500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:341@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Virginia Scarlett\nOnce considered a radical experime
|
|||
|
|
nt\, open source is now ubiquitous in the modern technology landscape\, an
|
|||
|
|
d appears to be here to stay. In the technology industry\, the Open Source
|
|||
|
|
Program Office (OSPO) is a common way to centralize a company’s open so
|
|||
|
|
urce strategy\, knowledge\, and diligence. Meanwhile\, OSPOs are just begi
|
|||
|
|
nning to take root in academia. This shift reflects the increased recognit
|
|||
|
|
ion by universities and other organizations that academic open source cont
|
|||
|
|
ributions are valuable\, numerous\, and worth sustaining. While guidance f
|
|||
|
|
or university OSPOs is emerging\, many questions remain about how academic
|
|||
|
|
support staff and their partners can best support their university’s st
|
|||
|
|
rategic priorities and their community’s needs.\n\nThe University of Cal
|
|||
|
|
ifornia (UC) OSPO Network is a groundbreaking project to establish a highl
|
|||
|
|
y collaborative network of OSPOs at UC campuses. We in the UC OSPO Network
|
|||
|
|
are working to develop infrastructure for open source education\, discove
|
|||
|
|
ry\, and sustainability at UC by pooling our resources and knowledge. To d
|
|||
|
|
evelop our strategic priorities and to assess the state of UC open source\
|
|||
|
|
, we conducted a survey in April 2025 of more than 180 UC-affiliated open
|
|||
|
|
source contributors. This survey reveals common challenges faced by open s
|
|||
|
|
ource contributors\, as well as potential remedies to those challenges. In
|
|||
|
|
addition to soliciting contributor perspectives\, the survey also solicit
|
|||
|
|
ed contributors’ GitHub usernames\, which we are now using to analyze UC
|
|||
|
|
open source repositories and their characteristics. Our survey will infor
|
|||
|
|
m other UC OSPO network projects\, promote community among open source ent
|
|||
|
|
husiasts at UC\, and serve as a template that other universities may draw
|
|||
|
|
from. This study will shed light on how and why academics contribute to op
|
|||
|
|
en source projects\, as well as some of the barriers that might be holding
|
|||
|
|
them back.
|
|||
|
|
LOCATION:329
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/334/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Talk
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T163000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T171500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:335@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:328
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Linux kernel test automation with kdevops
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T163000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T171500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:252@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Luis Chamberlain\nWe have a slew of ways to test the
|
|||
|
|
Linux kernel: selftests\, kunit\, and then we have a slew of subsystem spe
|
|||
|
|
cific tests. Intel 0-day has also done a fantastic job at helping find bug
|
|||
|
|
s. So has syzkaller. Some subsystems like filesystems and memory managemen
|
|||
|
|
t have really complex test frameworks though and have falling behind in au
|
|||
|
|
tomation. Is it possible to automate testing of complex subsystems? Should
|
|||
|
|
we? And what are the implications if we're successful?\n\nTo provide pers
|
|||
|
|
pective\, it takes roughly 10 years to stabilize a new Linux filesystem. B
|
|||
|
|
ut can we do better? The kdevops project was started with the goal of firs
|
|||
|
|
t of addressing automation of testing of complex subsystems such as filesy
|
|||
|
|
stems to help reduce the amount of time it takes to stabilize new filesyst
|
|||
|
|
ems or new filesystem features. The project aimed at supporting local virt
|
|||
|
|
ualization\, bare metal\, and all cloud provider support. Seven years late
|
|||
|
|
r since the project got started\, with the help of a lot of community coll
|
|||
|
|
aboration the project is now integral part not only of testing pipelines b
|
|||
|
|
ut also development workflows. The kdevops project now enables continuous
|
|||
|
|
integration for different subsystems starting with:\n\n * Linux modules\n
|
|||
|
|
* Linux radix tree\n * Linux filesystems: xfs\, btrfs\, ext4\n * Linux
|
|||
|
|
network filesystems: NFS\n * Linux selftests\n\nA dashboard of results i
|
|||
|
|
s now also updated automatically based on automatic tests: https://kdevops
|
|||
|
|
.org\n\nWhat have we learned from all this effort so far? And what lies ah
|
|||
|
|
ead for the roadmap? If you want to contribute and help how do you do that
|
|||
|
|
?
|
|||
|
|
LOCATION:328
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/301/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Observing Postgres in action using OpenTelemetry
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T163000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T171500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:289@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Basil Bourque\nWhile debugging in development\, or tr
|
|||
|
|
oubleshooting in production\, we need to monitor the conditions and behavi
|
|||
|
|
or of the various components in our systems. One of those components is th
|
|||
|
|
e database server. We need to look inside the black box that is our databa
|
|||
|
|
se server.\n\nMuch progress has been made in instrumenting\, generating\,
|
|||
|
|
collecting\, and exporting telemetry data (metrics\, logs\, and traces) to
|
|||
|
|
help us analyze our software systems’ performance and behavior. While v
|
|||
|
|
arious proprietary and open-source products have advanced this field of ob
|
|||
|
|
servability\, the industry has recognized the need to create a single coll
|
|||
|
|
ection of APIs\, SDKs\, and tools that can work in a vendor-neutral manner
|
|||
|
|
across the many implementations. The open-source community-driven project
|
|||
|
|
OpenTelementry is that solution.\n\nNow Postgres has gained support for O
|
|||
|
|
penTelemetry. Let's look at how observability works\, and how Postgres use
|
|||
|
|
s OpenTelemetry to provide the operations data that DBAs\, SysAdmins\, and
|
|||
|
|
developers need.
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/294/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Unconference
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T163000
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T171500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:368@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Copyleft- next / Articulating stakeholders and goals for FOSS
|
|||
|
|
licensing\n\n<a href="https://pad.sfconservancy.org/p/FOSSY25-ROOM-328">Pa
|
|||
|
|
d link</a>
|
|||
|
|
LOCATION:328
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Unconference
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T163000
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T171500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:378@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:What if git was nice to use? / Community Supporting Safety\n\n
|
|||
|
|
<a href="https://pad.sfconservancy.org/p/FOSSY25-ROOM-329">Pad link</a>
|
|||
|
|
LOCATION:329
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Agile/Scrum for Open Source Community Projects
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T163000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T171500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:351@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Tess Gadwa\nWhen Agile/Scrum is adapted effectively f
|
|||
|
|
or FOSS\, it holds significant advantages over the "benevolent dictator" m
|
|||
|
|
odel -- both in inclusivity and in building morale and participation.\n\nT
|
|||
|
|
he talk assumes:\n\n- Primarily online contributors\n- A mix of paid and v
|
|||
|
|
olunteer team members\n- Contributors at a range of skill levels\n- Contr
|
|||
|
|
ibutors in non-coding roles (documentation\, design\, and user research) a
|
|||
|
|
s well as development roles\n\nIt would build on lessons learned from Givi
|
|||
|
|
ng Map (givingmap.org) a grant-funded applied data visualization initiativ
|
|||
|
|
e that ran from 2020-21. However\, these best practices can be applicable
|
|||
|
|
to a broad range of projects.
|
|||
|
|
LOCATION:333
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/356/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:It's all about the ecosystem!
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T163000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T171500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:295@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Ben Ford\nYou may or may not remember Steve Ballmer's
|
|||
|
|
famous "developers\, developers\, developers" cheer from the late 90's\,
|
|||
|
|
but Microsoft has known something for a very long time that some OSS compa
|
|||
|
|
nies might learn from. When a tool or product exists in order to run third
|
|||
|
|
-party content -- that third-party content is the real value of your tool
|
|||
|
|
because without that content\, there's no reason to buy the product.\n\nCo
|
|||
|
|
mmercially supported open source projects often lose track of this real va
|
|||
|
|
lue. And all too often\, they learn that hard fact after community-hostile
|
|||
|
|
decisions decimate their ecosystem. SaltStack learned this the hard way\,
|
|||
|
|
so did Hashi\, Chef\, Redis\, and others.\n\nI'd like to talk about the i
|
|||
|
|
dea that the ecosystem is the product and the thing that you build and sel
|
|||
|
|
l only exists to support it. It's a subtle but important shift in mindset
|
|||
|
|
that I think helps keep focus on what's really important\, and I'm using i
|
|||
|
|
t to help direct the projects that I'm working on now.I\n\n\nSlide deck ca
|
|||
|
|
n be viewed here: https://binford2k.github.io/all_about_ecosystem/
|
|||
|
|
LOCATION:333
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/351/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Talk
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T163000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T171500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:330@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:328
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Break
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T171500
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T173000
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:258@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Break
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T171500
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T173000
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:256@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Opening Remarks
|
|||
|
|
DTSTART;TZID=US/Pacific:20250803T171500
|
|||
|
|
DTEND;TZID=US/Pacific:20250803T183000
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:228@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Closing Remarks
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Break
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T171500
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T173000
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:257@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:How do you solve a problem like iOS?
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T173000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T181500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:358@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Stephen Paul Weber\nThe user experience of those trap
|
|||
|
|
ped in the Apple ecosystem has for years been a problem for the open sourc
|
|||
|
|
e XMPP community. Not many community developers use that ecosystem\, and s
|
|||
|
|
o little development and testing goes towards it. After all we want to use
|
|||
|
|
freedomware operating systems on all our devices!\n\nYet it remains an is
|
|||
|
|
sue because\, as a communications network\, many people have friends and f
|
|||
|
|
amily they wish to connect with who use Apple devices. Not having a good\,
|
|||
|
|
freedom-respecting solution for those people means they often feel pulled
|
|||
|
|
towards proprietary walled gardens instead in order to be able to communi
|
|||
|
|
cate.\n\nI have been working on this problem for some time and will detail
|
|||
|
|
my approach using standard technologies to close most of this gap without
|
|||
|
|
any Apple devices at all\, the benefits of an extensible standard like XM
|
|||
|
|
PP on achieving this\, and how this might help other communities as well.
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/284/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:The big-endian RISC-V Linux Adventure
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T173000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T181500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:260@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Ben Dooks\nThe latest RISC-V ISA specification allows
|
|||
|
|
for runtime configuration of the data endian between little and big. Sinc
|
|||
|
|
e no one had done this before\, we decided to investigate how difficult it
|
|||
|
|
would be to get an prototype Linux implementation running in big endian o
|
|||
|
|
n an emulated RISC-V system such as under QEMU.\n\nThe talk goes from the
|
|||
|
|
description of the new ISA feature\, our initial analysis and the modifica
|
|||
|
|
tions to software such as the Linux kernel\, QEMU and OpenSBI that where n
|
|||
|
|
eeded. This then goes into the issues that we found and how to fix them.
|
|||
|
|
This includes kvm and how that works with mixed endian kvm instances\, and
|
|||
|
|
the modifications to kvmtool to make this work.\n\nWe conclude with how t
|
|||
|
|
he project went\, what we published and a call to arms to continue testing
|
|||
|
|
and fixing outstanding issues.
|
|||
|
|
LOCATION:328
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/302/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Reversing Metcalfe's Law: undermining the software-service–indus
|
|||
|
|
trial complex with .zip files
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T173000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T181500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:304@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Nathan Willis\nPortability and data sovereignty are o
|
|||
|
|
ften touted as critical principles for ensuring user privacy in the age of
|
|||
|
|
always-connected Internet services: the ability to archive and export you
|
|||
|
|
r information ensures that you cannot be held captive by a provider that f
|
|||
|
|
alls short on ethics or security. The tricky bit comes when users attempt
|
|||
|
|
to unpack this exported data and put it to proper use. This talk examines
|
|||
|
|
the free-software tools available to access common exported data sets and
|
|||
|
|
addresses the complexities faced when re-purposing account data or transfo
|
|||
|
|
rming it for use in free systems. Emphasis is placed on how desktop Linux
|
|||
|
|
distributions and server-side free-software networks could provide a bette
|
|||
|
|
r and more integrated experience. Datasets examined include email\, messag
|
|||
|
|
ing\, media\, bookmarks and favorites from discussion forums\, geolocation
|
|||
|
|
history\, health records\, contacts and calendars\, and social media post
|
|||
|
|
s.
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/320/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:open source for fun and profit
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T173000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T181500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:322@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Milo Oien-Rochat\nLearn how to convince your employer
|
|||
|
|
to open source internal projects and how to effectively contribute to ope
|
|||
|
|
n source projects while at work. I will share examples of open sourced pro
|
|||
|
|
jects and contributions to existing projects from my work at 3M Company.\n
|
|||
|
|
\nThis talk will cover exciting topics such as.\n* Employee contracts\n* F
|
|||
|
|
ind/set up an open source watering hole\n* Do your homework/arrive with a
|
|||
|
|
plan\n* Your attorney is a person too\n* Pro/con lists\n* The odds are in
|
|||
|
|
your favor\n* Get good at Git\n* Remove sensitive data (like email address
|
|||
|
|
es) from git repos\n* Make friends in IT\n* Set a trend make a friend
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/321/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Recipe for Discovery: Building the UC Open Source Repository Brows
|
|||
|
|
er From Scratch
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T173000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T181500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:336@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Juanita Gomez\nThe University of California’s netwo
|
|||
|
|
rk of Open Source Program Offices (OSPOs) launched last year\, bringing to
|
|||
|
|
gether six campuses (UC Santa Cruz\, Berkeley\, Davis\, Los Angeles\, Sant
|
|||
|
|
a Barbara\, and San Diego) to support open source research\, promote susta
|
|||
|
|
inability\, and establish best practices within academic environments. A k
|
|||
|
|
ey challenge in this effort is identifying and connecting open source proj
|
|||
|
|
ects across the system. Despite UC’s significant contributions to open s
|
|||
|
|
ource\, there is no centralized way to track these efforts\, making it dif
|
|||
|
|
ficult for researchers to find relevant projects\, for institutions to ass
|
|||
|
|
ess impact\, and for the broader community to engage with UC’s open sour
|
|||
|
|
ce work. To address this\, the UC OSPO Network is developing the UC Open S
|
|||
|
|
ource Repository Browser (UC ORB)\, a discovery tool designed to map and c
|
|||
|
|
lassify UC’s open source projects. This talk will explore the process of
|
|||
|
|
building the UC ORB\, from leveraging the GitHub API for data collection
|
|||
|
|
to integrating automated discovery with targeted outreach to the academic
|
|||
|
|
community. We will discuss the challenges of repository identification\, c
|
|||
|
|
ompare similar approaches\, and share lessons learned throughout the proce
|
|||
|
|
ss.
|
|||
|
|
LOCATION:329
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/357/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Talk
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T173000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T181500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:296@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:333
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Talk
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T173000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T181500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:324@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:328
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:DevOps is a Foreign Language (or Why There Are No Junior SREs)
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T173000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T181500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:323@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Joshua Lee\nDevOps has a notoriously steep learning c
|
|||
|
|
urve. Getting started in the field can feel like being dropped in a foreig
|
|||
|
|
n country without the ability to understand *anything* about the language.
|
|||
|
|
\n\nA language is more than just the syntax and semantic rules of the wor
|
|||
|
|
ds themselves. It also encompasses the shared culture of the speakers. Wit
|
|||
|
|
h the proliferation of programming languages as well as the deeply held cu
|
|||
|
|
ltural beliefs of the community\, it's easy to see that learning DevOps is
|
|||
|
|
like trying to learn a foreign language.\n\nI will review five foundation
|
|||
|
|
al hypotheses from the field of Second Language Acquisition and relate the
|
|||
|
|
se hypotheses back to the world of DevOps. DevOps practitioners\, trainers
|
|||
|
|
\, tool builders\, and learners should all come away with useful insights
|
|||
|
|
to apply to their practice.
|
|||
|
|
LOCATION:328
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/297/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Talk
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T173000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T181500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:280@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:329
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Building AI applications with Open-source database - PostgreSQL
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T173000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T181500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:303@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Gauri\nCurious about how to build AI applications wit
|
|||
|
|
h the tools you already know and love? This beginner-friendly session will
|
|||
|
|
show you how PostgreSQL can be the backbone of your AI workloads. We’ll
|
|||
|
|
break down key concepts like vector embeddings\, vector search\, and Retr
|
|||
|
|
ieval-Augmented Generation (RAG) in a simple\, easy-to-understand way. The
|
|||
|
|
n\, we’ll dive into how PostgreSQL’s native features and extensions ma
|
|||
|
|
ke it easy to store\, search\, and scale AI data — no special infrastruc
|
|||
|
|
ture needed.\nBest of all\, you'll see everything come to life through a h
|
|||
|
|
ands-on\, step-by-step demo where we’ll build a complete\, Generative AI
|
|||
|
|
application powered entirely by PostgreSQL.
|
|||
|
|
LOCATION:338
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/354/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Talk
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T173000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T181500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:302@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:329
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:Plausible Slop: Generative AI and Open Source Cybersecurity
|
|||
|
|
DTSTART;TZID=US/Pacific:20250802T173000
|
|||
|
|
DTEND;TZID=US/Pacific:20250802T181500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:352@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Dr. Kaylea Champion\nDespite speculation that the ris
|
|||
|
|
e of consumer-grade generative AI tools would trigger the development of m
|
|||
|
|
ore advanced cybersecurity attacks\, a more grounded view observes that in
|
|||
|
|
stead these synthetic text generating tools are eroding the social model o
|
|||
|
|
f open source cybersecurity through the low-effort extrusion of 'plausible
|
|||
|
|
slop': potentially significant and well-formed but ultimately erroneous a
|
|||
|
|
nd unwanted text. The presence of plausible slop in newcomer contributions
|
|||
|
|
in the form of bug and security reports to open source software packages
|
|||
|
|
requires substantial time commitment from scarce experts. These experts ar
|
|||
|
|
e caught in a double bind: their role dictates that they sort through what
|
|||
|
|
is truly dangerous and what is nonsense\, and they are charged with both
|
|||
|
|
welcoming problem reports from newcomers while also setting strong norms a
|
|||
|
|
gainst inauthentic reports. In this talk\, I report on my effort so far in
|
|||
|
|
vestigating plausible slop\, connect this challenge to previous historical
|
|||
|
|
challenges\, suggest avenues towards solutions\, and seek community feedb
|
|||
|
|
ack to shape next steps.
|
|||
|
|
LOCATION:333
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/348/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:The Future of Fixing Technology
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T173000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T181500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:284@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Denver Gingerich\nComputers and the internet had the
|
|||
|
|
potential to neutralize existing power structures and bring true equality
|
|||
|
|
in access to knowledge and the ability to control technology to the masses
|
|||
|
|
. While some power structures have changed\, new ones have emerged that t
|
|||
|
|
hreaten to undo the very fabric of modern society. These new power struct
|
|||
|
|
ures promote misinformation\, put control of technology in the hands of an
|
|||
|
|
elite few\, and prevent the masses from customizing or improving the devi
|
|||
|
|
ces that they rely on to communicate with the rest of the world.\n\nIn the
|
|||
|
|
early days of the internet\, there was a feeling of excitement about its
|
|||
|
|
endless possibilities. There was a sense that it could indeed give us unf
|
|||
|
|
ettered access to the best information available\, and we could use that t
|
|||
|
|
o improve our technology and our lives. However\, events like the Eternal
|
|||
|
|
September and many less defined epochs showed that the internet on its ow
|
|||
|
|
n could not maintain its utopic promise. We needed a plan\, a way of stan
|
|||
|
|
ding up to power structures and other influences\, one that put critical t
|
|||
|
|
hinking\, cultural sensitivity\, and user agency at the forefront.\n\nThe
|
|||
|
|
future of fixing our technology and adapting it to each of our individual
|
|||
|
|
unique needs and preferences could go a few different ways. In this talk\
|
|||
|
|
, we'll explore the history of fixing our technology\, where we're at now\
|
|||
|
|
, and what it will take to make this individualized technology future a re
|
|||
|
|
ality.\n\nAmong other topics\, we'll discuss "the plan" for getting there\
|
|||
|
|
, laying out a few concrete steps that we'll need to take to get where we
|
|||
|
|
want to go. Along the way we'll talk about how power structures get disma
|
|||
|
|
ntled and rebuilt through technological change\, and how we can collective
|
|||
|
|
ly temper the seemingly inevitable swings between different factions of th
|
|||
|
|
e wealthy elite controlling technology relied upon and available to the ma
|
|||
|
|
sses\, so that we eventually approach the asymptote of actual freedom and
|
|||
|
|
agency in the computing realities of the average user.
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/312/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Talk
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T173000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T181500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:318@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:No description
|
|||
|
|
LOCATION:333
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:RAGtime with Postgres: AI Power with pgvector and Retrieval-Augmen
|
|||
|
|
ted Generation
|
|||
|
|
DTSTART;TZID=US/Pacific:20250801T173000
|
|||
|
|
DTEND;TZID=US/Pacific:20250801T181500
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:290@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Speaker: Jimmy Angelakos\nRetrieval-Augmented Generation (RAG)
|
|||
|
|
is a powerful paradigm in application development with AI. In this talk\,
|
|||
|
|
we'll demonstrate how to leverage PostgreSQL with pgvector to combine the
|
|||
|
|
strengths of vector similarity search with Large Language Models (LLMs).\
|
|||
|
|
n\nAs the speaker is a Postgres nerd (not an AI expert)\, we'll explain in
|
|||
|
|
simple terms how to dip your toes into AI while leveraging our favorite d
|
|||
|
|
atabase -- from the perspective of a database person learning to work with
|
|||
|
|
these new tools.\n\nWe'll walk through: \n\n- How to use pgvector to stor
|
|||
|
|
e and search vector embeddings (and what those are)\n- How to connect thes
|
|||
|
|
e capabilities with AI LLMs to build intelligent applications. \n- Some pr
|
|||
|
|
actical tips for implementation\, including configuration\, indexing strat
|
|||
|
|
egies\, and scaling considerations\n- How to reduce dependency on expensiv
|
|||
|
|
e external AI services by using open-source models while maintaining contr
|
|||
|
|
ol over costs and infrastructure\n\nTo demonstrate these concepts in actio
|
|||
|
|
n\, we'll look at a real-world example of building a developer assistance
|
|||
|
|
system that helps teams understand their codebase.
|
|||
|
|
LOCATION:327
|
|||
|
|
URL:http://2025.fossy.us/schedule/presentation/295/
|
|||
|
|
END:VEVENT
|
|||
|
|
BEGIN:VEVENT
|
|||
|
|
SUMMARY:FOSSY 2025: Social Event
|
|||
|
|
DTSTART;TZID=US/Pacific:20250731T190000
|
|||
|
|
DTEND;TZID=US/Pacific:20250731T220000
|
|||
|
|
DTSTAMP:20260223T173351Z
|
|||
|
|
UID:379@2025.fossy.us
|
|||
|
|
CATEGORIES:
|
|||
|
|
DESCRIPTION:Official Thursday Night Event at Punch Bowl Social\n\n340 SW M
|
|||
|
|
orrison St Suite 4305\, Portland\, OR 97204\nJust quick ~15 minute Max rid
|
|||
|
|
e from PSU. All attendees are invited!
|
|||
|
|
URL:http://2025.fossy.us
|
|||
|
|
END:VEVENT
|
|||
|
|
END:VCALENDAR
|