Add core meeting notes 2026-03-04 (#13)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: Matt Fisher <3608264+mfisher87@users.noreply.github.com>
Co-authored-by: Matt Fisher <mfisher87@gmail.com>

Author: 3 people

meeting-notes/20260304-core/index.md

@@ -0,0 +1,73 @@
+---
+title: "Jupyter Community Committee Meeting"
+description: |
+  A bi-weekly gathering of the Community Committee.
+date: "2026-03-04"
+author:
+  - name: "The Community Committee"
+categories:
+  - "Meeting notes"
+tags: [meeting-notes]
+---
+
+# Community Committee Meeting (2026-03-04)
+
+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
+
+* Matt
+* Celeste Horgan
+* April
+* Jason
+* Rosio
+
+
+### Action items
+
+- [ ] ASAP! Need to email EC to champion getting money to continue the community workshops initiative. Need to get scope first via conversation with Deb.
+    - [ ] April: Schedule discussion with Deb about scoping funding for next iteration. How much should we expect each workshop to cost? Can we have more workshops? Meet at JCB meeting in 4 weeks.
+    - [ ] Rosio: Email EC to ask for them to champion next iteration of workshops with the board -- know in advance (from previous action item) roughly how much money we're asking for.
+    - [ ] Celeste: Raise this at tomorrow's board meeting. Ping us on Zulip.
+- [ ] April: Ask LF (Deb) to set up a meeting to iterate on how we do workshops with LF. All of us meet with Deb and workshop organizers. Target early April.
+- [ ] Matt: Add link to 2024(5?) community survey results to our team compass.
+    - https://blog.jupyter.org/community-building-report-project-jupyter-5a0fd7c8b08d
+- [ ] April: Reach out to Naomi -- we want to be able to change our own meeting on the calendar. Ask for permissions. Is there a way we can give small groups of people, like our committee, access to create and manage their own meetings without giving full admin? Do you have training around how our community can use this and enable broader use by the community.
+
+
+### Agenda & notes
+
+- Connecting with Jupyter Foundation's community efforts
+    - Overview of JCB activities
+        - [Jupyter community workshops](https://jupyter.org/community#jupyter-community-workshops)
+            - Wildly successful
+            - High-impact strategic work
+            - Low budget (relatively), usually come under budget due to donations (space, travel funding, catering, etc.)
+            - Need to continue iterating, figuring out how to do this in collab with LF (this is the first year trying that out).
+        - JupyterCon oversight role -- now LF taking over
+            - Happy to play a role in the events!
+            - 2025, there was a program committee + LF. But no connective tissue for non-program committee questions. How can the JCB help improve this? Connect community outreach, planning, with JCon event planning.
+                - Celeste: Big topic!
+                - Let's keep thinking about it together.
+        - [Community Survey](https://blog.jupyter.org/community-building-report-project-jupyter-5a0fd7c8b08d) (and acting on feedback from the survey)
+
+        - Reporting out to EC
+            - We've not been good about this!
+            - We moved to [publicizing our meeting minutes](https://jupyter.org/community-committee/meeting-notes/), though. So that's something :)
+        -
+    - Foundation board
+        - Posted some off-the-record comments in Zulip
+        - Next 3-6 months, plug in to the JCB. Walk softly. Become community liaison.
+            - How do we feel about inviting Celeste in to our various spaces, e.g. Zulip, this meeting?
+            - Full member of our committee?
+            - Celeste: Let's think more along the lines of the "community liaison" board role and how to create a healthy community<>board relationship regardless of who is in the role.
+            - Is participation in the community committee a mechanism for keeping the community<>board relationship healthy?
+            - Celeste: Someone could be both board liaison _and_ a full member of the committee. But perhaps it shouldn't be required. Opportunity to set a pattern and clearly define what a liaison is and isn't. Formalizing and scoping the role is important.
+- Punted to next meeting:
+    - Lahari: Metrics
+    - April: JupyterHub roadmapping workshop

myst.yml

@@ -25,6 +25,7 @@ project:
     - rule: "link-resolves"
       keys:
         - "https://docs.google.com/document/d/**"
+        - "https://blog.jupyter.org/**"
       severity: "warn"