Skip to content

Commit 59d5ded

Browse files
slandathcholdgraf
slandath
and
choldgraf
authored
EC Meeting Notes (#178)
Co-authored-by: Chris Holdgraf <choldgraf@gmail.com> Signed-off-by: Tom Slanda <jesus_slanda@yahoo.com>
1 parent 0779175 commit 59d5ded

1 file changed

Lines changed: 176 additions & 0 deletions

File tree

‎docs/meeting_notes/2026.md‎

Lines changed: 176 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,181 @@
11
# Meeting notes from 2026
22

3+
## 2026 June 9
4+
5+
### Attendees
6+
7+
| Executive Council Member Voting Rep | Company | Attended |
8+
| ------------- | ------------- | ------------- |
9+
| Afshin Darian | QuantStack | X |
10+
| Jake Diamond-Reivich | Mito Labs | |
11+
| Chris Holdgraf | 2i2c | X |
12+
| Martha Cryan | Plotly | X |
13+
| Rick Wagner | SDSC/UCSD | X |
14+
| Zach Sailer | Apple | X |
15+
16+
### Notes
17+
18+
* Distinguished Contributors Program
19+
* Facing low nominations and unclear ownership, the team is considering downsizing the program to one slot per year or eliminating it entirely. Naomi will gauge the Community Building Committee's interest in taking over the program; otherwise, it may be phased out.
20+
* Payment Procedures
21+
* The group is exploring standardizing payments for contributors, with Chris suggesting adopting the Linux Foundation’s process for speaker honoraria. Naomi will consult with her finance partner regarding the best mechanism for these disbursements.
22+
* Governance Documentation
23+
* Any changes to governance page wording will now require independent approval from both the Software Steering Council (SSC) and the Executive Council (EC) via a formal pull request process.
24+
* Council Repository
25+
* Naomi will communicate the transition to the new "Councils" repository to the community this week. This repository will serve as the centralized contact point for the SSC and EC.
26+
* SciPy Conference Coordination
27+
* The team agreed to focus SciPy presentations on user-facing subprojects (JupyterLab, JupyterHub, JupyterBook) rather than governance. Chris will coordinate efforts to prevent messaging overlap.
28+
* Renaissance Fund & Sponsorship
29+
* The team is navigating grant submissions for the CZI EOSS-inspired "Renaissance Fund." They are currently seeking clarification on Linux Foundation fiscal sponsorship rates (6-9%) and whether the million-dollar revenue threshold includes member organization funding.
30+
* Maintainer Travel Fund
31+
* To foster trust and relationship building, the EC is working to secure a budget line item specifically for small-group, in-person maintainer meetings. Naomi will provide a comparison of administrative requirements to determine the most streamlined reimbursement process.
32+
* Jupyter AI Unification
33+
* Zach is leading efforts to unify three parallel server-side document state implementations. While significant progress has been made in resolving interpersonal dynamics and project gatekeeping, the team is waiting to formalize Jupyter AI as a subproject until the technical streams are fully consolidated.
34+
* Open Source Collaboration Challenges
35+
* The group recognized a need for better "leadership education" regarding open source workflows. They identified a common friction point where corporate contributions are often limited to short, concentrated sprints, which conflicts with the long-term, iterative nature of maintaining open source software.
36+
37+
---
38+
## 2026 May 12
39+
40+
### Attendees
41+
42+
| Executive Council Member Voting Rep | Company | Attended |
43+
| ------------- | ------------- | ------------- |
44+
| Afshin Darian | QuantStack | X |
45+
| Jake Diamond-Reivich | Mito Labs | X |
46+
| Chris Holdgraf | 2i2c | X |
47+
| Martha Cryan | Plotly | X |
48+
| Rick Wagner | SDSC/UCSD | |
49+
| Zach Sailer | Apple | X |
50+
51+
### Notes
52+
53+
* AI Security and Project Glasswing
54+
* The team addressed conflicting industry data regarding AI security tools, specifically noting inconsistent results regarding the effectiveness of "Mythos." Naomi plans to share information regarding the upcoming "Project Glasswing" (under Alpha Omega) with the governing board.
55+
* Website Redesign Strategy
56+
* To avoid past bottlenecks, the project will be divided into three distinct areas: content structure (Community Building Committee), professional design (funded web team), and technical implementation. A hybrid approach, similar to the one used for PyTorch, may be employed to integrate custom features like interactive demos into the new site.
57+
* Standardized Funding Process
58+
* The EC is formalizing a process for community members to request funding outside of standard proposal cycles. Requests will be submitted via GitHub issue templates in a consolidated repository, acting as a "first-pass" filter before the EC presents them to the governing board for a final vote.
59+
* Repository and Governance Consolidation
60+
* The team is establishing a new repository named "Councils" under the main Jupyter organization. This will serve as a single point of contact for both the Executive Council and the Software Steering Council. Naomi is tasked with setting this up and implementing the necessary forms by the end of the week.
61+
* Subproject Governance
62+
* The group discussed the need for clearer criteria on when a subproject's expansion of scope requires a formal, project-wide vote versus when they can exercise autonomy. While recent additions like JupyterLite followed proper organizational procedures, there is a recognized need to mitigate ecosystem-wide risks.
63+
* Legal and Onboarding
64+
* Naomi clarified that initiatives must undergo formal legal onboarding to be transferred to LF Charities. Most immediate concerns have been resolved, as JupyterBook and JupyterLite are already integrated into the system.
65+
* LLM Contribution Policies
66+
* Due to the sensitivity of the topic and concerns regarding safety—specifically for foreign nationals participating in public threads—the team decided against an open workshop. Instead, they will form a small working group to draft guidelines through facilitated sessions, aiming for a balance between ethical oversight and corporate collaboration.
67+
* Managing Competitive Dynamics
68+
* The team discussed improving relationships with Posit, a recent foundation member. They intend to actively welcome Posit's participation in subproject meetings and community events while maintaining a professional awareness of competitive market dynamics.
69+
70+
---
71+
## 2026 April 28
72+
73+
### Attendees
74+
75+
| Executive Council Member Voting Rep | Company | Attended |
76+
| ------------- | ------------- | ------------- |
77+
| Afshin Darian | QuantStack | X |
78+
| Jake Diamond-Reivich | Mito Labs | X |
79+
| Chris Holdgraf | 2i2c | X |
80+
| Martha Cryan | Plotly | X |
81+
| Rick Wagner | SDSC/UCSD | |
82+
| Zach Sailer | Apple | X |
83+
84+
### Notes
85+
86+
* Leadership & Governance Structure
87+
* Jason is set to become the new Executive Director. His role will complement his existing funded work. He will be invited to the next call to clarify his reporting lines (Board vs. EC) and overall priorities.
88+
* There is an ongoing discussion regarding whether the Executive Council (EC) should evolve into a technical advisory committee modeled after the Linux Foundation (LF). Naomi prefers a simplified structure, though this creates tension with the current, less formal Software Steering Council.
89+
* Chris suggested the ED should prioritize general strategic expertise and open-source community experience over deep technical knowledge of Jupyter, citing Steven Diabal (former GNOME Foundation director) as an ideal profile.
90+
* Members are defining their roles as "ambassadors" to gather information on strategic changes across the project. There is a push to automate these updates using tools like GitHub release scrapers rather than manual reporting.
91+
* Operations & Budgeting
92+
* The EC approved 2-3K from their 25K discretionary budget to centralize Read the Docs access under a parent organization, part of a broader account consolidation initiative led by Matthias.
93+
* The group voted 5-to-1 in favor of migrating documentation to a unified Jupyter.org platform, noting that the current documentation working group appears to be defunct.
94+
* Jake raised concerns about the foundation development team’s accountability, pipeline visibility, and the goal of recruiting two new Premier members. Chris advised delivering this feedback to Mike constructively to avoid defensiveness.
95+
* Meredith (foundation team) will be going on maternity leave in early July, which will likely lead to Mike becoming more hands-on with the Jupyter team in the interim.
96+
* Community Initiatives & Guidelines
97+
* The group is establishing guidelines for LLM usage in project contributions. They aim to draft a "Community Discussion on Using LLMs to Contribute to Project Jupyter" to gather input without imposing rigid restrictions.
98+
* A revised governance proposal by Zach was well-received and will be posted in the governance repository.
99+
* To reduce confusion, the team is working to centralize communication channels and standardize where project updates and governance items are posted.
100+
* The group discussed the need for formal succession planning for EC members, noting that current member participation often conflicts with their primary job responsibilities.
101+
102+
---
103+
## 2026 April 21
104+
105+
### Attendees
106+
107+
| Executive Council Member Voting Rep | Company | Attended |
108+
| ------------- | ------------- | ------------- |
109+
| Afshin Darian | QuantStack | X |
110+
| Jake Diamond-Reivich | Mito Labs | X |
111+
| Chris Holdgraf | 2i2c | X |
112+
| Martha Cryan | Plotly | |
113+
| Rick Wagner | SDSC/UCSD | X |
114+
| Zach Sailer | Apple | X |
115+
116+
### Notes
117+
118+
* Executive Council Meetings & Structure
119+
* Rick and Naomi discussed the distinction between the Executive Council (EC) and the Foundation Board. Rick proposed limiting EC meetings to when specific issues arise that fall outside the Board's purview, rather than meeting on a fixed, frequent schedule.
120+
* The EC agreed to shift to a bi-weekly schedule with one-hour sessions, replacing the previous 30-minute weekly cadence.
121+
* Technical & Ecosystem Developments
122+
* The team addressed the complexity of managing multiple server implementations, specifically the challenges surrounding Jupyter Server and Jupyverse.
123+
* Zach provided an update on the Jupyter AI subproject, noting the ongoing difficulties in navigating technical decisions across different implementation approaches.
124+
* Event Planning & Coordination
125+
* Naomi confirmed she will manage the public announcement and posting of details for the upcoming Jupyter AI Summit.
126+
* Rick shared that he has started a new role at Argonne National Laboratory (DOE), focusing on the intersection of supercomputing, AI, and energy.
127+
128+
---
129+
## 2026 April 14
130+
131+
### Attendees
132+
133+
| Executive Council Member Voting Rep | Company | Attended |
134+
| ------------- | ------------- | ------------- |
135+
| Afshin Darian | QuantStack | X |
136+
| Jake Diamond-Reivich | Mito Labs | X |
137+
| Chris Holdgraf | 2i2c | |
138+
| Martha Cryan | Plotly | |
139+
| Rick Wagner | SDSC/UCSD | |
140+
| Zach Sailer | Apple | X |
141+
142+
### Notes
143+
144+
* Jupyter AI Integration & Technical Tensions
145+
* Both Jupyter AI and Jupyter Lite are now officially integrated into Jupyter front-ends, though split efforts across multiple repositories have caused some confusion.
146+
* Competing server-side document approaches by David Brochart and David Q are blocking Jupyter AI progress and creating a "choosing-a-winner" dependency issue.
147+
* Zach will draft two parallel JEPs to address these underlying technical challenges, prioritizing a fix for the server-side documents problem despite an acknowledged conflict of interest in authoring them.
148+
* To consolidate efforts and move forward, the team will focus on shipping and iterating rather than upfront perfection, which includes a proposal to make Jupyter AI contrib an official sub-project.
149+
* Jupyter AI Developer Summits
150+
* The team finalized the name "Jupyter AI Developer Summit" for two upcoming events in different locations, with potential timing adjustments to accommodate attendance.
151+
* Jake will manage a free registration system for the summits with Zach acting as backup, and initial travel funding arrangements have been discussed.
152+
153+
---
154+
## 2026 April 7
155+
156+
### Attendees
157+
158+
| Executive Council Member Voting Rep | Company | Attended |
159+
| ------------- | ------------- | ------------- |
160+
| Afshin Darian | QuantStack | |
161+
| Jake Diamond-Reivich | Mito Labs | X |
162+
| Chris Holdgraf | 2i2c | |
163+
| Martha Cryan | Plotly | X |
164+
| Rick Wagner | SDSC/UCSD | X |
165+
| Zach Sailer | Apple | X |
166+
167+
### Notes
168+
169+
* Cybersecurity & Project Planning
170+
* Rick and Jake plan to delegate cybersecurity policy implementation to Joe Lucas. To free up his technical capacity, they proposed creating a new role dedicated to handling stakeholder engagement and community communication.
171+
* Major updates will be shared through monthly blog posts rather than frequent minor notifications. Rick offered to present updates on Joe's behalf if necessary.
172+
* A meeting will be scheduled with Rick, Jake, Martha, Joe (Nvidia), and other working group members like Matthias to align on freeing up Joe's capacity.
173+
* Community, Marketing & Accessibility
174+
* Ely from Bloomberg was identified as a key contact for Jupyter accessibility. Martha noted that achieving full WCAG compliance on landing pages requires significant engineering effort and ongoing maintenance.
175+
* Jake plans to introduce a strategy to the marketing subcommittee to create reusable content (event updates, release notes). Member representatives can share these directly with their internal OSPOs and board members.
176+
* The team aims to launch a monthly newsletter or blog post to track OSPO initiatives and balance marketing efforts to attract new attendees to specialized events (like security workshops) while retaining foundation companies like AWS and Bloomberg.
177+
178+
---
3179
## 2026 March 31
4180

5181
### Attendees

0 commit comments

Comments
 (0)