---
title: "Jupyter Community Committee Meeting"
description: |
A bi-weekly gathering of the Community Committee.
date: "2026-03-11"
author:
- name: "The Community Committee"
categories:
- "Meeting notes"
tags: [meeting-notes]
---

# Community Committee Meeting (2026-03-11)

Please add new agenda items under the `New agenda items` heading!

- [Previous meetings](https://jupyter.org/community-committee/meeting-notes/)
- [Jupyter Community Committee](https://jupyter.org/governance/list-of-standing-committees-and-working-groups/#jupyter-community-building) handy links:
- [GitHub repo](https://github.com/jupyter/community-committee)

## Attendees

* Jake Diamond-Reivich (aka JDR, visiting from EC and JMS)
* April
* Matt
* Jason
* Rosio

### Action items

- [ ] Matt: Update meeting notes template to include standing items. **Initiative reports**. Metrics is the first! Jason & Lahari.
- [ ] Matt: Add initiatives to community compass

### Agenda & notes

* Marketing connection
* Looked at the Jupyter Content Calendar together
* Something that's missing in Marketing strategy: amplifying more community content!
* Matt: +100
* Similar relationship to the Foundation as ours
* JF Marketing Committee + JF Community Committee
* JCB is exploring a "liaison" relationship
* JMS are members of the Foundation Marketing Committee.
* JDR's ask: What do we need / need promoted?
* Workshops!
* Allowing community members to upload to Jupyter YouTube channel
* Jake: Yes! Goal to create frictionless path for community members to share cool stuff. Make it easy to submit. If someone has something to share and doesn't know how, tell them to reach out to Jake / JMS ([email]([e-mail])). Better solution coming soon.
* Expectation is not that the thing to share is polished -- the JMS will help figure out where to share and what revisions might be needed, etc. They're there to help, not just to put a fished product on a platform.
* Jason: Need better guidelines on expectations about what can be shared and how JMS helps.
* Contributor / community member spotlight! **Jake's goal is to have the first person selected this week!**
* Community stats (metrics)
*
* Liaison with the foundation (Celeste)
*
* Community workshops
* 2026!
* Meet with workshop organizers + LF for a retrospective to get feedback, plan next iteration!
* Jupyter-endorsed 3rd-party-funded workshops
* JCB Initiatives / big picture planning
* Mostly community workshops right now
* What's next?
* How do we involve the community in planning / executing initiatives?
* How do we start DOING?
* Choose an initiative and leader(s)
* April: Having two leaders, create accountability!
* Ongoing iniatives:
* Workshops (active)
* Community call (maintenance?)
* Frequency -- monthly/2-monthly intead of quarterly
* Facilitators -- find a 2nd leader
* Kirstie, Lahari, April, Matt
* "Let's pick a facilitator for next time (we'll support you)" at the end of each community meeting
* **1st NEW INITIATIVE**: Jason & Lahari - Metrics/statistics
* Create a page for this active initiative on the compass -- who's leading it, how to get involved.
* **2nd NEW INITIATIVE**: Matt & April & Rosio - Welcome mats
* What do we need in the short term? Guided by metrics.
* Communication tools: Discourse declining, Zulip growing. Do we need Discourse? What is the role of our various conversation spaces?
* Consistency of the welcome mat.
* Celeste's experience and interests in the k8s world are here.
* New Zulip channel `#community`
* Should we name it `#community-building` to help it hone its focus just a bit more? Not sure...