# JupyterHub community workshop draft

[team compass issue]( https://github.com/jupyterhub/team-compass/issues/805)

## Due: Sunday, 14. Sept, end of day anywhere on earth

1. Workshop Name: JupyterHub/Binder roadmap workshop

2. up to 3 organizers:

- Name, affiliation, email
- Arielle Bennett, The Alan Turing Institute, [e-mail]
- Min Ragan-Kelley, UC Berkeley, [e-mail]
- Raniere Silva, GESIS, [e-mail]

- [name=Kirstie] Would Simon or Raniere consider being an organizer too? (Simon we'd love for you to bring a TRE connection? Would you run a UK hub maybe? We could fund! Or Raniere - are you building up a connection to TRE work at GESIS?)
- [name=Simon] Probably can't help with hosting, but if we want to discuss TREs I can help organise
- [name=Raniere] GESIS approved the provision of conference spaces for the workshop at Cologne, Germany that is served by three airports (Cologne-Bonn, Dusseldorf, and Frankfurt) and train (including Eurostart). This is subject to availability. People at GESIS are interested in the TRE.
- [name=Raniere] Raniere will be the point of contact for logistics in Cologne.
- [name=Kirstie] What about Arielle as another organizer to support on logistics? [I think we should try to not have an all male organizing team - and I know that's cynical but it doesn't look great....]
- [name=Kirstie] (Kirstie & Lilli at BIDS would also be very supportive on logistics, but its silly to have Min and Kirstie on the organizers list together!)
- [name=Kirstie] Other options are Yuvi? Georgiana? Representing a 2i2c lens?

**3. Describe the goal/topic of the workshop in 1-3 sentences:**

Developing and documenting a roadmap for JupyterHub projects. Inviting maintainers and users to discuss where JupyterHub, repo2docker, and BinderHub should be going and what resources we have to move it forward, and publicly documenting/communicating this plan for improved visibility. The scope will cover a subset of projects across the JupyterHub org (jupyterhub, z2jh, tljh, repo2docker, binderhub, possibly JupyterHealth), depending on which participants we get.

**4. How does the workshop involve strategic work related to Project Jupyter?**

The roadmap is the public view of JupyterHub's strategic plan. It helps deployers know what to expect in upcoming releases, contributors know where they can help, and maintainers know what work is expected of each other. Involving community stakeholders in the roadmapping process ensures that we are building something useful together.

**5. How will this event grow the size and/or health of the Jupyter contributor community, including underserved or underrepresented contributors?**

Our users, those who install JupyterHubs, are eager to more deeply engage with the JupyterHub community. One of the biggest community-engagement features requested from the JupyterHub community has been a roadmap to anticipate and engage with active JupyterHub development. The workshop will aim to fill this gap, and involve this user community's needs in guiding JupyterHub's future development efforts. By exploring a remote-first timezone-spanning format, we engage the largest community community we can, and can use it as a model to develop future workshops.

**6. Approximate Event Date**

Must avoid overlap with JupyterCon. A buffer period has been set from October 20 to November 20; do not schedule during this time unless you are co-locating with JupyterCon.

To give us time to prepare, the end of the window: 2026-02-27/28 (exact dates to be determined by availablity of participants)

**7. Proposed Venue:**

2 days, remote-first with some in-person conference rooms, one in California (UC Berkeley), another in Cologne, Germany (GESIS). Remote, multi-timezone participation will be modeled on the Turing Way Book Dash.

- UC Berkeley / BIDS
- [name=Raniere] GESIS at Cologne, Germany
- Raniere will be the local contact point

| Germany time | Berkeley time | Note |
| --- | --- | --- |
| 08:00 - 12:00 | | Hack time |
| 12:00 - 13:00 | | Break |
| 13:00 - 16:00 | | European time session |
| 16:00 - 17:00 | | Break |
| 17:00 - 20:00 | 08:00 - 11:00 | Synchronous session |
| 20:00 - 21:00 | 11:00 - 12:00 | Break |
| | 12:00 - 15:00 | East US time session |

* [name=Kirstie] What about a UK hub and a CA hub:
* Daytime UK: synchronous time zone specific collaboration / hacking / some other activity (please edit!)
* Evening UK/morning CA: synchronous global collaboration - everyone in one zoom experience (so can use breakout rooms etc, but we're talking to each other as a whole group)
* Afternoon CA: synchronous time zone specific collaboration / hacking / some other activity (please edit!)

(Repeat for 2 days!)

**8. How many people do you anticipate attending the event?**
10-20?

(Shall we maybe make an invite list? We could put that in the issue? Doesn't have to go in the application but would be good to let folks know that we want them to come!!)

- [name=min] we can reach out to individuals, but I think we should also have a form posted on the forum so folks can express interest without being invited.

**9. What is your proposed budget? When responding, please include a total amount you will not exceed and a high-level line-item breakdown of expense categories. Is there any other funding being provided from other sources?**

Not more than $20k. Estimate $1.5k per traveling participant, plus $200 for food and $50 for remote participants. Total $3k for accomodating childcare and accessibility. Some small cost for stickers/rewards to send to remote participants. Venues are provided by hosts UC Berkeley and GESIS at no cost. That would let us support travel for about 10 participants.

most likely ~10, plus food support (childcare?), including for remote participants.

* 3 nights accomodation: $1000 / person
* Not-too-far flight (to UK / EU or CA): $600 / person
* Food budget per person: $200 in person, $50 remote (a nice take away dinner)
* Budget for childcare / accessibility: $3000 (a pot to dip into)
* Venue for free from BIDS / AI Futures Lab, UK venue??
* [name=Raniere] Venue for free from GESIS
* [name=Arielle] We might also want to include a small amount of funding for some nice merch that is easily postable - stickers but could also do other *useful* items as well - easy to send to remote folks;
If 10 people travelled that would be around $16000 + $2000 +

10. By submitting, you agree to the Codes of Conduct for both The Linux Foundation and Project Jupyter.

## Planning

### Date

* Last week of February - 25 / 26 February
* Location:
* Berkeley - AI Futures Lab - Min to book
* GESIS - Raniere to book a room

* Workshop capacity
* Physical in Berkeley:
* Physical in Cologne:
* Remote participants: