Jupyter Community Committee Meeting

Community Committee Meeting (2026-04-01)¶

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

• Previous meetings

• Jupyter Community Committee handy links:

  • GitHub repo

Attendees¶

• April

• Matt

• Jason

• Rosio

Action items¶

• Matt (carried over): Update meeting notes template to include standing items. Initiative reports. Metrics is the first! Jason & Lahari.

• Matt (carried over): Add initiatives to community compass

• Matt: Open issues for welcome mat initiative

• ?: Reach out to Celeste, ask her to lead definition of the liaison role and give her a date of April 15?

• April: Miro board for workshops retro

Agenda & notes¶

• New Zulip channel for “community” (move more of our discussions into the public)¶

• Did we follow-up with Celeste to invite her as a committee member?

  • Establish a liaison role

    • Is the “best” version of this having the liaison also a full member on the committee?

  • Want Celeste to also be a member of the community committee as an individual?

  • We need to close this thread

    • What’s the “best” version of the liaison role?

      • Matt: I think it would be ideal if the liaison creates a productive relationship with the board via full membership, but may not always be possible

      • April: Either is fine, depends on person

      • Jason: It’s a one-way door. Maybe transition from liaison after leaving the board?

      • Rosio: Leaning more towards liaison and committee membership being mutually exclusive

      • Decision: Let’s start with liaison not a committee member, and re-evaluate

    • Celeste: Official role definition

• Initiative: Community stats /metrics (Jason, Lahari)

  • Jason: No updates

  • Don’t feel ready to spin up yet -- busy with marketing stuff

  • Marketing committee shares interest in public metrics, not so much community health metrics (e.g. time to first response on issue)

  • Jason and Lahari to come back with some certainty around when this can start up

  • Backburner it for today, revisit next meeting.

• Deb is arranging a community workshop retro!

  • Invite Celeste

  • Shooting for month of April

  • Deb can schedule

  • Workshops got positive feedback from participants and organizers!

  • We own agenda & notes capture. Sketch:

    • Our goals:

      • What works & didn’t work, expected/unexpected for LF?

      • Same for workshop organizers

      • Figure out what the next iteration looks like

    • From LF & organizers (same questions):

      • Add your answers to the collaborative space. Be sure to label with your name. 2x2 matrix with post-its in Miro (April). Different colored post-its for workshop organizers vs LF (downside is feeling like you have to represent your group)? Send a list of questions beforehand

        • Worked?

        • Didn’t work?

        • Expected?

        • Unexpected?

        • Hard or stressful?

        • Feedback: How did the responsibility grid work out, and what should be changed?

        • Feedback: Thoughts about the budget?

          • E.g. community organizers might want to focus on content more than logistics, how can LF do more?

      • Group discussion: Notes in a shared doc, generate action items (not commitments, things we need to have follow-up conversations above):

        • How do we improve the experience next time?

    • Follow up with workshop organizers!

• Initiative: Welcome mat (Matt, Rosio, April)

  • Matt & April: No updates

  • Ready to spin up

  • What does this look like?

    • How do we meet?

      • Part of this meeting or start a new meeting?

        • Split this meeting in half, one for sync all together, one for subgroups

      • Alternate weeks with this meeting?

      • Work async?

        • Rosio :+1:

      • Decision: April and Matt can co-work together and record tasks somewhere for async

    • How do we represent work?

      • GitHub issues, label for our initiative, & project board?

        • Matt, April, Rosio :+1:

    • How do we outreach about the work?

      • Zulip in the new public community channel

        • What we have done? Kind of like announcing releases of new things

        • What can the community do? What meetings you can join? What tasks need help / feedback?

  • Scope

    • Educational resources

      • Roadmapping!

    • Recommendations for best practices

    • Examples of well-implemented welcome mats / related things

      • https://antennapod.org/contribute/

      • https://github.com/2i2c-org/initiatives

    • Welcome mat for this initiative

    • Managing quantity and quality of attention in the AI era

    • Navigating across / mapping the community & subprojects

      • how do we link up with documentation working group?

      • do we work on global documentation? (jupyter.org -- has metrics tooling already, can gauge effectiveness)

    • Contributing to Project Jupyter & Jupyter subprojects applying best practices

    • Identify quick wins on the PJ website -- needed work for a long time.

      • Foundation board has been interested in funding the work.

      • We can scope the work and help do outreach to find folks to do the work.

      • What other questions need to be answered (e.g. ownership of the website)

    • April’s 2i2c colleagues feeling lost looking for how to get more involved in Jupyter project.

      • Get feedback from them?

    • Process: Evaluate, recommend, implement

    • Phases: PJ website, subprojects, ...?

  • Next steps: Marinate. Break this up in to chunks so we can complete work

• Initiatives: Do we focus on one initiative at a time at the start?

  • Matt: :+1:

    • Worried a failure mode could be trying to do too many things at once, communication failures, struggling to schedule meetings, etc. One initiative to start with helps us establish patterns that work before trying to parallelize multiple initiatives.

• Availability

  • Rosio: Uncertainty about availability going forward. Update as she learns more!

  • Matt: Unavailable next meeting April 15th. Out all week.