Skip to content

Commit a8780ba

Browse files
github-actions[bot]mfisher87pre-commit-ci[bot]
authored
Add core meeting notes 2026-03-11 (#15)
* Add meeting-notes/20260311-core/index.md * Update meeting-notes/20260311-core/index.md * Spelling * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * Change email link to inline code Resolves link check failure * Downgrade github link check errors to warnings Rate limiting... --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Matt Fisher <3608264+mfisher87@users.noreply.github.com> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
1 parent af1fec2 commit a8780ba

2 files changed

Lines changed: 85 additions & 0 deletions

File tree

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
---
2+
title: "Jupyter Community Committee Meeting"
3+
description: |
4+
A bi-weekly gathering of the Community Committee.
5+
date: "2026-03-11"
6+
author:
7+
- name: "The Community Committee"
8+
categories:
9+
- "Meeting notes"
10+
tags: [meeting-notes]
11+
---
12+
13+
# Community Committee Meeting (2026-03-11)
14+
15+
Please add new agenda items under the `New agenda items` heading!
16+
17+
- [Previous meetings](https://jupyter.org/community-committee/meeting-notes/)
18+
- [Jupyter Community Committee](https://jupyter.org/governance/list-of-standing-committees-and-working-groups/#jupyter-community-building) handy links:
19+
- [GitHub repo](https://github.com/jupyter/community-committee)
20+
21+
22+
## Attendees
23+
24+
* Jake Diamond-Reivich (aka JDR, visiting from EC and JMS)
25+
* April
26+
* Matt
27+
* Jason
28+
* Rosio
29+
30+
31+
### Action items
32+
33+
- [ ] Matt: Update meeting notes template to include standing items. **Initiative reports**. Metrics is the first! Jason & Lahari.
34+
- [ ] Matt: Add initiatives to community compass
35+
36+
37+
### Agenda & notes
38+
39+
* Marketing connection
40+
* Looked at the Jupyter Content Calendar together
41+
* Something that's missing in Marketing strategy: amplifying more community content!
42+
* Matt: +100
43+
* Similar relationship to the Foundation as ours
44+
* JF Marketing Committee + JF Community Committee
45+
* JCB is exploring a "liaison" relationship
46+
* JMS are members of the Foundation Marketing Committee.
47+
* JDR's ask: What do we need / need promoted?
48+
* Workshops!
49+
* Allowing community members to upload to Jupyter YouTube channel
50+
* 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 `jupyter-media-strategy@googlegroups.com`). Better solution coming soon.
51+
* 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.
52+
* Jason: Need better guidelines on expectations about what can be shared and how JMS helps.
53+
* Contributor / community member spotlight! **Jake's goal is to have the first person selected this week!**
54+
* Community stats (metrics)
55+
*
56+
* Liaison with the foundation (Celeste)
57+
*
58+
* Community workshops
59+
* 2026!
60+
* Meet with workshop organizers + LF for a retrospective to get feedback, plan next iteration!
61+
* Jupyter-endorsed 3rd-party-funded workshops
62+
* JCB Initiatives / big picture planning
63+
* Mostly community workshops right now
64+
* What's next?
65+
* How do we involve the community in planning / executing initiatives?
66+
* How do we start DOING?
67+
* Choose an initiative and leader(s)
68+
* April: Having two leaders, create accountability!
69+
* Ongoing initiatives:
70+
* Workshops (active)
71+
* Community call (maintenance?)
72+
* Frequency -- monthly/2-monthly instead of quarterly
73+
* Facilitators -- find a 2nd leader
74+
* Kirstie, Lahari, April, Matt
75+
* "Let's pick a facilitator for next time (we'll support you)" at the end of each community meeting
76+
* **1st NEW INITIATIVE**: Jason & Lahari - Metrics/statistics
77+
* Create a page for this active initiative on the compass -- who's leading it, how to get involved.
78+
* **2nd NEW INITIATIVE**: Matt & April & Rosio - Welcome mats
79+
* What do we need in the short term? Guided by metrics.
80+
* Communication tools: Discourse declining, Zulip growing. Do we need Discourse? What is the role of our various conversation spaces?
81+
* Consistency of the welcome mat.
82+
* Celeste's experience and interests in the k8s world are here.
83+
* New Zulip channel `#community`
84+
* Should we name it `#community-building` to help it hone its focus just a bit more? Not sure...

myst.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,7 @@ project:
2525
- rule: "link-resolves"
2626
keys:
2727
- "https://docs.google.com/document/d/**"
28+
- "https://github.com/**"
2829
- "https://blog.jupyter.org/**"
2930
severity: "warn"
3031

0 commit comments

Comments
 (0)