Skip to content

Commit 3fc892f

Browse files
github-actions[bot]pre-commit-ci[bot]mfisher87
authored
Add core meeting notes 2026-02-18 (#11)
* Add meeting-notes/20260218-core/index.md * Update meeting-notes/20260218-core/index.md * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * Add context --------- 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>
1 parent 0cfbc50 commit 3fc892f

1 file changed

Lines changed: 75 additions & 0 deletions

File tree

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
---
2+
title: "Jupyter Community Committee Meeting"
3+
description: |
4+
A bi-weekly gathering of the Community Committee.
5+
date: "2026-02-18"
6+
author:
7+
- name: "The Community Committee"
8+
categories:
9+
- "Meeting notes"
10+
tags: [meeting-notes]
11+
---
12+
13+
# Community Committee Meeting (2026-02-18)
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+
* Rosio
25+
* April
26+
* Matt
27+
* Lahari
28+
* Jason
29+
30+
31+
### Action items
32+
33+
- [ ] Reach out to EC & Kirstie Whitaker: What's the current state of thinking about metrics for the Jupyter community?
34+
- https://ec.jupyter.org/#contacting-the-executive-council
35+
- [ ] Jason: Confirm that the charter is ok to publish
36+
- [ ] Matt: Open PR for charter to Jupyter governance page after Jason thumbs up. Remove the DEI charter. Open as draft.
37+
- Include in the title that we're incorporating DEI into the Community Committee to try and avoid any emotional reaction about removing DEI charter. "Merge DEI and Community Building WG into new Standing Committee". Or should we do it in multiple steps, starting with updating our charter, and months later remove DEI charter?
38+
- DECISION: Do it all at once, but do outreach. Post in the issue "We're doing this! Thank you for your feedback!"
39+
- Post on Zulip.
40+
- PRESENT AT COMMUNITY MEETING. Rosio / April will be in charge of this.
41+
- Reference issue: https://github.com/jupyter/governance/issues/293
42+
- [ ] Matt: **Link** to charter on Team Compass (after published on Juptyer governance page)
43+
- [ ] Matt: Page about community workshop program on team compass
44+
45+
- [ ] Lahari and Rosio will chat offline to prep for facilitating community call
46+
47+
### Agenda & notes
48+
49+
- Last actions:
50+
- Lahari: Invite member of 8knot team to our next meeting. We’ll spend the first 30 minutes understanding how we can use 8knot.
51+
- **What do we want to measure?** Specific metrics we care about. And how to measure across entire community / subprojects.
52+
- https://chaoss.community/kbtopic/all-metrics-models/
53+
- Lahari wrote a 1-pager with recommendations - will find and share
54+
- https://docs.google.com/document/d/1-DADjV9Oixv93vGDdVBfGi4qOFgPWAGJmY0ve9Vv2Z0/edit?tab=t.0#heading=h.ny6mjy1wrqyt
55+
- Need to reach out to EC & Kirstie Whitaker first to ask about how metrics are currently being used / gathered.
56+
- ~~Lahari: Request final feedback on the charter from team members in Zulip! (done!)~~
57+
- Review the charter. Finalize!
58+
- Review Rosio's comments (done & resolved!)
59+
- Community call! Wednesday February 25, 9AM PT
60+
- Rosio thinks we're good to go logistically, a few more messages need to be posted on zulip
61+
- Feeling uncomfortable hosting due to sickness.
62+
- Lahari will facilitate
63+
- Community workshop status
64+
- LF and JupyterHub community have this covered! Nothing for us to do right now.
65+
- Lahari: How do we measure the impact/success of the workshops? Will the organizers of the workshop come up with a report or something once it’s over?
66+
- Does LF survey people?
67+
- The JupyterHub community will share a report-out afterwards to give us a sense of impact!
68+
- Jason: Here are our success measures (for the community workshops program as a whole)
69+
- Create a system with public documentation for current and future event series
70+
- Receive at least 3 high-quality proposals from the CFP
71+
- Host 3 events in 2025 with volunteer hosts in partnership with LF
72+
- Ensure blog posts are published from each event detailing strategic work and community building impact
73+
- Stay within the budget
74+
- Initiatives
75+
- Didn't have time, will get to it next time :)

0 commit comments

Comments
 (0)