Submit talk at All Things Open 2026

[KirstieJane]

Hi team!

@jasongrout suggested that we submit a talk on Voices of Jupyter Hub and our Roadmapping work to All Things Open 2026 (ere's the zulip chat)

The deadline is TODAY so erm..... shall I maybe have a try at it?

[KirstieJane]

All Things Open 2026 - Call For Speakers

The All Things Open selection committee is seeking talks from established technologists
with many years of experience, technologists and community members that may be new to
"open", and talks from traditionally underrepresented groups and organizations. In short,
we're seeking a diverse lineup as we firmly believe it delivers the most value to attendees.

---

Primary Speaker Information

• Primary Speaker's Email (required) kirstie.whitaker@berkeley.edu
• Primary Speaker's Name (required) Kirstie Whitaker
• Primary Speaker's Company (required — write "n/a" if not applicable) Berkeley Institute for Data Science
• Primary Speaker's Job Title (required) Executive Director
• Primary Speaker's Company Website (required — write "n/a" if not applicable) https://bids.berkeley.edu
• Primary Speaker's Bio (required) TBD
• Primary Speaker's Twitter URL N/A
• Primary Speaker's LinkedIn URL https://www.linkedin.com/in/kirstiewhitaker
• Primary Speaker's Personal Website https://bids.berkeley.edu/people/kirstie-whitaker
• Primary Speaker's Phone Number (required) [not for public posting!]
• Headshot (required — minimum 500x500) [on my laptop]
• Primary Speaker's Speaking Credentials (required) TBD

---

Diversity & Inclusion

• Underrepresented community identification (required — private/anonymized)

  Please indicate any of the following that you identify with (not exhaustive):

  • Gender

---

Additional Speaker

• Do you have another speaker or secondary contact (e.g. an assistant)? (required)
  • No X
  • Yes

Talk Details

• Talk Title (required) TBD
• Talk Abstract (required) TBD
• Talk Difficulty (required) Introductory / Intermediate / Advanced 👈 Any suggestions here?
• Talk Session Type/Length (required)
  • 5–8 minute "burst" track session ❌
  • 10 minute plenary keynote
  • 30 minute track session ❌
  • Two hour deep dive
  • Four hour workshop
• Which track is your talk most appropriate for? (required) Open source projects
• Secondary track option Community

---

Additional Considerations

• Consider for Inclusion & Diversity in Open Source event? (required) Yes

  The annual Inclusion & Diversity program is a one-day stand-alone event on Sunday,
  October 18. Selecting "Yes" enters your talk for this in addition to the main
  conference programming on October 19 & 20.

• Consider for Community Leadership Summit (CLS)? (required) Yes

  CLS is co-located with All Things Open on Sunday, October

• Can this talk be construed as a sales pitch? (required) No

[Arielle-Bennett]

Suggested titles:

Paving the way while riding it: roadmapping for open source projects - lessons from JupyterHub

Finding a community voice for open source projects

10 things JupyterHub wishes it had known before planning a roadmapping workshop

If we have some inkling of which way we'd like to go for an abstract I can write something up

I would say our talk is intermediate but this depends on the time available as to how much detail we can go into - I wouldn't expect a beginner to be starting with either topic in open source but neither will it be very technical

[Arielle-Bennett]

Okay, the below works best as a 30 min talk I think - will cross-post to Zulip too

Title: Finding a Community Voice: How JupyterHub is Learning to Speak as an Open Source Project

Abstract:
What does it take for an open source project to sound like itself? To have a voice that not only reflects the existing maintainers efforts and perspectives, but captures goals and aims for the project, draws in new contributors, and keeps them returning?

In open source projects, where time, focus, and resources are often scarce, this type of initiative can easily be deprioritized in favor of fire-fighting, or find projects lacking in contributor skills sets to make them effective.

JupyterHub, critical open source scientific infrastructure, democratizes the creation of, and access to, interactive computing environments by providing secure, scalable, and user-friendly platforms that enable individuals, teams, and organizations to craft customized environments for exploring data, developing code, and advancing knowledge without barriers. Used by millions across the globe, it is currently building out its community voice through a series of initiatives to not only set directions for the project, but build dialogue with users, and diversify its contributors as well.

This talk reflects on what JupyterHub has learnt from building these rituals, doing the deep dive, and having the discussions to develop a consistent voice, and where it might go next. If you have ever struggled with community building, culture reflections, or contributor onboarding and are looking to learn from , this talk is for you.

[Arielle-Bennett]

Update: this has been submitted with @KirstieJane as a co-speaker. We can always adjust this later if needed I think!