Hey 
here’s another quick update on what stood out to me from the executive council and the jupyter foundation. Sorry that there was such a large gap in time since my last update - I am doing my best, but also have two small children and a very demanding job 
.
The last few months have been quite busy with a few major initiatives hitting milestones within the Jupyter Executive Council. This is partially why I didn’t have the time to write these updates! Here are a few things that stand out:
Community workshops awardees
Community workshops are an important part of bringing Jovyans together in a way that is more localized in place and topic than JupyterCon. The Community Building Working Group selected their first round of workshops for funding from the Foundation. Check out the blog post about this below:
Community proposals awardees
Jupyter community funding proposals are a new mechanism we are experimenting with for getting Foundation resources directly into the hands of maintainers and subprojects through targeted grants. The board of the Jupyter Foundation selected the recipients of the first round of Jupyter community funding proposals! We’re working with the Linux Foundation to coordinate distributing these funds now. See this blog post for more details:
We completed JupyterCon 2025!
Oh my gosh, it is so much more work organizing an international conference than we all expected. But after a lot of heroic work from the organizing committee and the board, we successfully had JupyterCon 2025! Personally, I was really proud of the exciting ideas that came out of this conference, it was such a high-quality group of attendees and speakers. It’s hard to overstate how much organizing and work this was.
Find all of the JupyterCon videos here
And here’s a fun highlights video complete with a synth-y house soundtrack and inevitable discussion about AI.
Executive Council elections are open
We’ve been coordinating with LF to hand-off the administration of Jupyter’s executive council elections. E-mails to each of the sub-project councils should have gone out already, and voting should end in a few days.
The governance docs should be a bit more navigable
We’ve updated Jupyter’s governance docs to use Jupyter Book’s new release, which includes improving some of the data infrastructure behind our directories so that it’s easier to quickly answer questions like “what are the Jupyter subprojects and who is on the leadership team of each?”. Find that here:
Where are our priorities right now?
I think everybody is still recovering a bit from JupyterCon (and heading into the productivity black hole of December), but right now our priorities are thinking about what we should learn from 2025 and how we can use that to make better plans for 2026. To me, the biggest thing we’re still working on is learning to delegate and empower others rather than doing it ourselves. We’ve made a few experiments towards this and I think they almost always pay off. I’d like to see the EC (and the Foundation) do more delegation of responsibility and use the Foundation to offer resources needed to carry out that responsibility. Hopefully we can make progress on these ideas in the coming year.
OK that’s it for me for now!
This is a monthly experiment from Chris as part of the JEC’s efforts to open up communication and channels of transparency with the JEC and the board. He’ll do his best to keep posting these updates. He’s time-boxing them to about 15 minutes in an effort to keep them sustainable. This means they’ll be rough! He’d love feedback about whether this is useful or how they could be better.