| Time | Activity |
|---|---|
| 00:00 - 00:20 | Scene Setting |
| 00:20 - 00:40 | Group Connections |
| 00:40 - 02:15 | Group Discussions & Shareouts |
| 02:15 - 02:30 | Break |
| 02:30 - 03:20 | Contributing to JupyerHub as user | 03:20 - 03:30 | Wrap up & next steps |
JupyterHub administrators & deployers know a lot about deploying JupyterHub in different settings...
...but there hasn't always been a clear pathway to feed this knowledge and insight back to the project team
This workshop is part of an experiment to connect the project community & deployers on a regular cadence
We want to provide spaces for administrators and deployers across the community to get to know each other...
...& explore possible pathways for them to directly contribute their expertise back to JupyterHub
This workshop was inspired by the recommendations from the "Voices of JupyterHub" report, part of CZI EOSS grant
Read more at voicesofjupyterhub.orgmycology.com
Or come to the talk on Wednesday morning (11:35am, Royal Room) βοΈ
Pick some of the following questions to discuss
Add notes to the shared notes document as you chat
Pick someone to report back to the main group
We'll remind you to switch questions
If we're a smaller group, we'll go through the questions all together
If you could go back and give yourself one piece of advice before your first deployment, what would it be?
What's the most surprising infrastructure or operational challenge you've faced with JupyterHub?
What are some of the common challenges you see with other deployments? How could these be tackled upstream or collectively?
If you could add one feature to JupyterHub tomorrow, what would make your life easier? How could you help with it's development?
What are some of the security or compliance requirements that significantly shaped your implementation?
How do you learn about JupyterHub updates? How well does this fit with your organisations operations and needs?
How would you describe your relationship with the JupyterHub project and community?
How do you collect feedback from your users? How do they, or you, pass on this feedback to the project? How could this process be smoother?
What would motivate you to become more involved with JupyterHub development or community? What are the practical steps the community could take to support that journey?
If we're a large group, we'll split up into groups again
JupyterHub documentation currently lists JupyterHub deployments
But we'd like to share more about these!
Both to celebrate all the hard work which goes into running different types of deployment... π
...& to inspire and support future deployers of JupyterHub π‘
Check out the headings in the "Case Study Template" section of the shared notes
Are there any aspects missing you'd like to see included?
Would you or your team be willing to complete one on your deployments?
Wednesday November 5, 2025, 11:35am PST
Royal Room
Check out the links on the next slide π
Keep an eye out for blog posts covering this event soon!
Fill out this form to share feedback & stay in touch https://forms.gle/gxYHkyaBbHEGpZXm6