diff --git a/.github/workflows/preview.yml b/.github/workflows/preview.yml
index 680f7112..33dcd9f7 100644
--- a/.github/workflows/preview.yml
+++ b/.github/workflows/preview.yml
@@ -150,6 +150,7 @@ jobs:
cp -r dist/client/screenshots "${PREVIEW_DIR}/"
cp -r dist/client/deck "${PREVIEW_DIR}/"
cp -r dist/client/deck-template "${PREVIEW_DIR}/"
+ cp -r dist/client/open-source-communities "${PREVIEW_DIR}/"
find dist/client -maxdepth 1 -type f \( -name "*.svg" -o -name "*.png" -o -name "*.ico" -o -name "*.webmanifest" -o -name "*.webp" \) -exec cp {} "${PREVIEW_DIR}/" \;
cp "${PREVIEW_DIR}/index.html" "${PREVIEW_DIR}/404.html"
diff --git a/public/open-source-communities/Lexend-Black.woff2 b/public/open-source-communities/Lexend-Black.woff2
new file mode 100644
index 00000000..583820c6
Binary files /dev/null and b/public/open-source-communities/Lexend-Black.woff2 differ
diff --git a/public/open-source-communities/Lexend-Bold.woff2 b/public/open-source-communities/Lexend-Bold.woff2
new file mode 100644
index 00000000..dad8b9df
Binary files /dev/null and b/public/open-source-communities/Lexend-Bold.woff2 differ
diff --git a/public/open-source-communities/Lexend-Regular.woff2 b/public/open-source-communities/Lexend-Regular.woff2
new file mode 100644
index 00000000..b454f26d
Binary files /dev/null and b/public/open-source-communities/Lexend-Regular.woff2 differ
diff --git a/public/open-source-communities/Lexend-SemiBold.woff2 b/public/open-source-communities/Lexend-SemiBold.woff2
new file mode 100644
index 00000000..1376230e
Binary files /dev/null and b/public/open-source-communities/Lexend-SemiBold.woff2 differ
diff --git a/public/open-source-communities/challenges-grid.webp b/public/open-source-communities/challenges-grid.webp
new file mode 100644
index 00000000..964919d0
Binary files /dev/null and b/public/open-source-communities/challenges-grid.webp differ
diff --git a/public/open-source-communities/first-contribution-screenshot.png b/public/open-source-communities/first-contribution-screenshot.png
new file mode 100644
index 00000000..b7dc4b6c
Binary files /dev/null and b/public/open-source-communities/first-contribution-screenshot.png differ
diff --git a/public/open-source-communities/index.html b/public/open-source-communities/index.html
new file mode 100644
index 00000000..0263445b
--- /dev/null
+++ b/public/open-source-communities/index.html
@@ -0,0 +1,1124 @@
+
+
+
+
+ Open Source Is Not Just Code - Sinduri Guntupalli
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Open Source Is Not Just Code
+
Designing Communities That Actually Scale
+
Sinduri Guntupalli
+
Press S for speaker notes
+
+
+
+
+
+
+
+ speaker
+
About Me
+
+
+
+
+
+
+
Sinduri Guntupalli
+
Sr Developer Programs Engineer, OSPO team at Dynatrace
+
+
+
+
+
+ ✷
+ 5+ years in Drupal: developer, then Product Manager
+
+
+ ✷
+ Volunteer organizer across Drupal Austria, Drupal Switzerland, and beyond
+
+
+ ✷
+ Now in the OSPO team at Dynatrace
+
+
+ ✷
+ Building offon.dev, a vendor-neutral community to sustain open source contributors and grow the maintainers of tomorrow
+
+
+
+
+
+
+
+
+
+
Part I
+
I
+
The Burden
+
◆
+
Most projects don't fail on code. They fail under invisible weight.
+
+
+
+
+
+
+
+ context
+
The Comfortable Myth
+
+
+ ✷
+ The myth: success comes from code quality
+
+
+ ✷
+ Just ship better code, and the rest follows
+
+
+ ✷
+ Mostly wrong
+
+
+
+
+
+
+
+ reality
+
What Actually Kills Projects
+
+
+ ✷
+ Unclear contribution paths
+
+
+ ✷
+ Expectations never written down
+
+
+ ✷
+ A few absorb all the pressure
+
+
+ ✷
+ Fragile, then it stalls
+
+
+
+
+
+
+
+
+
+
+ reframe
+
A Socio-Technical System
+
+
+ ✷
+ A socio-technical system
+
+
+ ✷
+ Code and community are one system
+
+
+ ✷
+ Community design matters as much as code
+
+
+
+
+
+
+
+ problem
+
The Maintainer Trap
+
+
+ ✷
+ Work piles onto a few people
+
+
+ ✷
+ The hero maintainer burns out
+
+
+ ✷
+ A single point of failure is a design flaw
+
+
+
Example: Rust
+
Topic-focused teams (compiler, language, libraries, tooling, infrastructure) each own their area independently. A leadership council coordinates across teams. Ownership is spread by design, so no single person carries the whole project.
+
+
+
+
+
+
+
+
Part II
+
II
+
The Fellowship
+
◆
+
The work is too much for one person. It has to be shared.
+
+
+
+
+
+
+
+
+ framework
+
Four Levers That Decide Whether a Project Lasts
+
+
+
+
+
+
+
+
Governance
+
Who decides, and how. Make decision-making explicit before you need it.
+
+
+
Contributor Experience
+
How easy and rewarding it is to help. Lower the cost of showing up.
+
+
+
Recognition
+
Whether people's work is seen and valued. Most community labor is invisible.
+
+
+
Local Community
+
Where belonging actually forms. Global projects still need local homes.
+
+
+
+
+
+
+
+
+ lever 1
+
Governance
+
+
+ ✷
+ Decide how you will decide, early
+
+
+ ✷
+ Put shared functions under a neutral body
+
+
+ ✷
+ Spread maintainer roles across people
+
+
+ ✷
+ Give conflict a clear path
+
+
+
Example: Apache Software Foundation
+
Project management committees elect committers based on merit. Individuals represent themselves, not employers. Decisions happen in the open on mailing lists: if it wasn't recorded, it didn't happen.
+
+
+
+
+
+
+
+ lever 2
+
Contributor Experience
+
+
+ ✷
+ Lower the cost of a first contribution
+
+
+ ✷
+ Give newcomers a clear place to start
+
+
+ ✷
+ Visible path to trusted contributor
+
+
+ ✷
+ If it is confusing, they quietly leave
+
+
+
Example: Kubernetes
+
Published contributor ladder: member to reviewer to approver, with clear expectations at each step. Good first issues. Mentoring cohorts. A graceful way to step back when life gets busy.
+
+
+
+
+
+
+
+
+
+ lever 2 · from experience
+
My First Contribution
+
+
+ ✷
+ 2021, during Covid, new to the community
+
+
+ ✷
+ 45 min just to open the issue, scared of being judged
+
+ ✷
+ Most labor is invisible: review, triage, docs, mentoring
+
+
+ ✷
+ Invisible work gets undervalued
+
+
+ ✷
+ Record who did the work, sponsors included
+
+
+
Example: Drupal Contribution Credit System
+
A public record of who did what, across code and the invisible work. Contribution becomes visible instead of assumed.
+
+
+
+
+
+
+
+ lever 3
+
Why Recognition Changes Behavior
+
+
+ ✷
+ Tie recognition to real work
+
+
+ ✷
+ Companies get visible standing for what they fund
+
+
+ ✷
+ It becomes routine, not a favor
+
+
+
When a company treats contribution as part of the actual work, with real time and budget behind it, the alignment becomes real and it lasts. Good incentive design beats good intentions every time.
+
+
+
+
+
+
+
+ lever 4
+
Local Community
+
+
+ ✷
+ Global projects need local belonging
+
+
+ ✷
+ Pair global events with local ones
+
+
+ ✷
+ Local events lower the barrier
+
+
+ ✷
+ "Come for the code, stay for the community"
+
+
+
Example: Drupal
+
Pairs DrupalCon globally with local, volunteer-run camps. Small and accessible by design. That's where new people get pulled in and where most new organizers learn the ropes.
+
+
+
+
+
+
+
+
Part III
+
III
+
The Road Ahead
+
◆
+
What to prioritize, what AI changes, and what you can actually do.
+
+
+
+
+
+
+
+ priorities
+
What to Do Now vs Later
+
+
+
+ optimize early
+
✷Clear contribution paths and onboarding
+
✷Explicit, written expectations
+
✷Distributing authority before the load gets heavy
+
Cheap now. Expensive to fix later.
+
+
+ safe to delay
+
✷Heavy formal governance and elaborate process
+
✷Complex tooling and automation
+
✷Over-structuring a community that is still small
+
Heavy process on a tiny project can strangle it before it grows.
+
+
+
+
+
+
+
+
+ nuance
+
Good Advice Needs the Right Partner
+
+
+
+
"Be welcoming to everyone"
+
Works when paired with triage, so maintainers can keep up.
+
+
+
"Move fast"
+
Works when paired with shared decision rights, so people stay aligned.
+
+
+
"Document everything"
+
Works when paired with clear ownership, so the docs stay current.
+
+
+
Context decides whether a practice helps. The practices aren't the problem; the pairing is.
+
+
+
+
+
+
+ AI
+
Help and Hazard
+
+
+
+ where ai helps
+
✷Lowers the barrier to a first contribution
+
✷Speeds up docs, translation, and issue triage
+
✷Could ease the "privilege of free time" open source depends on
+
+
+ where ai strains
+
✷Low-effort contributions can overwhelm reviewers
+
✷The cost shifts from author to maintainer
+
✷Access is unequal. AI can become a new privilege.
+
+
+
+
AI doesn't replace community design. It raises the stakes. Share the cost and skill. Build it into contributor experience.
+
+
+
+
+
+
+
+ mental model
+
Thrive vs Decay
+
+
+
+ thriving projects
+
✷Share decisions
+
✷Make it easy to help
+
✷Recognize the work
+
✷Build local belonging
+
+
+ decaying projects
+
✷Concentrate decisions
+
✷Leave contributors guessing
+
✷Let invisible work go unseen
+
✷Stay purely global
+
+
+
The drift is slow and quiet. That's exactly why it's easy to miss.
+
+
+
+
+
+
+ your turn
+
What You Can Realistically Influence
+
+
You don't need to become a full-time maintainer.
+
+ ✷
+ Document one unclear process
+
+
+ ✷
+ Review a first contribution
+
+
+ ✷
+ Credit invisible work out loud
+
+
+ ✷
+ Help one local event
+
+
These are small structural acts. They compound.
+
+
+
+
+
+
+
+
+
+ close
+
Open Source Is Not Just Code
+
+
+
+ ✷
+ The system around the code is what scales
+
+
+ ✷
+ Design it on purpose
+
+
+ reality check
+
+ ✷
+ No quick fix
+
+
+ ✷
+ You control your corner, not the whole
+
+
+ ✷
+ Changing defaults is slow, and that is normal
+
+
+ ✷
+ Start with one lever
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ community
+
Join OffOn.dev
+
+
+ ✷
+ A welcoming space for everyone who loves open source: learners, contributors, maintainers, writers, designers, translators, and organizers
+
+
+ ✷
+ Built to sustain the people behind open source and grow the maintainers of tomorrow
+
+
+ ✷
+ Play Challenges: hands-on, scenario-driven challenges built around real open source tools. Runs entirely in GitHub Codespaces.
+
+
+ 
+ 
+ 
+ 
+ 
+ 
+