|
1 | 1 | # Meeting notes from 2025 |
2 | 2 |
|
| 3 | +## May 27th 2025 |
| 4 | + |
| 5 | +### Attendees |
| 6 | +- Ana Ruvalcaba |
| 7 | +- Rick Wagner |
| 8 | +- All others were unavailable today |
| 9 | + |
| 10 | +### Notes |
| 11 | + |
| 12 | +- Brief meeting, no quorum |
| 13 | +- Discussed JupyterCon and future/forward looking planning for event |
| 14 | + |
| 15 | +## May 20th 2025 |
| 16 | + |
| 17 | +### Attendees |
| 18 | + |
| 19 | +- Ana Ruvalcaba |
| 20 | +- Afshin Darian |
| 21 | +- Rick Wagner |
| 22 | +- Jason Grout |
| 23 | +- Zach Sailer |
| 24 | + |
| 25 | +### Notes |
| 26 | +- Triage of [EC GH Project Board](https://github.com/orgs/jupyter-governance/projects/8): made progress on reviewing priorities and backlog |
| 27 | +- Discussion of public communication from the EC [issue](https://github.com/jupyter-governance/ec-team-compass/issues/127). Brainstormed principles and practices for more frequent communication. Requires continued work. Once we land on principles we’ll publicly announce. |
| 28 | +- Review and test of GH Sponsor link [https://github.com/sponsors/jupyter](https://github.com/sponsors/jupyter) |
| 29 | +- Discussion and review of mission/vision/values for Project Jupyter |
| 30 | +- Discussion of engaging with a consultant |
| 31 | + |
3 | 32 | ## May 13th 2025 |
4 | 33 |
|
5 | 34 | ### Attendees |
|
13 | 42 |
|
14 | 43 | ### Notes |
15 | 44 |
|
16 | | -* Spent time triaging [Executive Council Team Compass](https://github.com/jupyter/executive-council-team-compass/issues) and [Jupyter Governance repo](https://github.com/jupyter/governance/issues) (shared repo with Software Steering Council). The EC will spend time weekly on triaging moving forward. |
17 | | -* Discussion of trademark enforcement. Discussion of resolving open issues and working more closely with LF lawyer. |
18 | | -* Discussion of security concern in the following issue: [https://github.com/jupyter/nbformat/pull/411\#pullrequestreview-2837103539](https://github.com/jupyter/nbformat/pull/411#pullrequestreview-2837103539) \- next step will be review by the security subproject |
19 | | -* Discussion of interactions with the Foundation Governing board and how to better work with that group. |
| 45 | +* Spent time triaging [Executive Council Team Compass](https://github.com/jupyter/executive-council-team-compass/issues) and [Jupyter Governance repo](https://github.com/jupyter/governance/issues) (shared repo with Software Steering Council). The EC will spend time weekly on triaging moving forward. |
| 46 | +* Discussion of trademark enforcement. Discussion of resolving open issues and working more closely with LF lawyer. |
| 47 | +* Discussion of security concern in the following issue: [https://github.com/jupyter/nbformat/pull/411\#pullrequestreview-2837103539](https://github.com/jupyter/nbformat/pull/411#pullrequestreview-2837103539) \- next step will be review by the security subproject |
| 48 | +* Discussion of interactions with the Foundation Governing board and how to better work with that group. |
20 | 49 | * Discussion of the Technical Subcommittee meeting of the Jupyter Foundation and working toward a software quality program for subprojects to opt individual published packages and repos backstopped by Foundation funded work for maintenance and security issues. |
21 | 50 |
|
22 | 51 | ## May 6th 2025 |
|
120 | 149 |
|
121 | 150 | ## Attendees |
122 | 151 |
|
123 | | -* Rick Wagner |
124 | | -* Ana Ruvalcaba |
125 | | -* Afshin Darian |
126 | | -* Jason Grout |
127 | | -* Zach Sailer |
| 152 | +* Rick Wagner |
| 153 | +* Ana Ruvalcaba |
| 154 | +* Afshin Darian |
| 155 | +* Jason Grout |
| 156 | +* Zach Sailer |
128 | 157 | * Chris Holdgraf (second half) |
129 | 158 |
|
130 | 159 | ### Notes |
131 | 160 |
|
132 | | -* NSF Proposal, follow up on logistics related to this task |
133 | | -* SSC discussion surrounding how we can encourage better collaboration among teams. One idea proposed was various groups meeting together regularly, essentially combining development calls for subprojects. |
| 161 | +* NSF Proposal, follow up on logistics related to this task |
| 162 | +* SSC discussion surrounding how we can encourage better collaboration among teams. One idea proposed was various groups meeting together regularly, essentially combining development calls for subprojects. |
134 | 163 | * Jupyter Community Call discussion about how to encourage more frequent meetings. Currently the Jupyter DEI team is planning to host these once a quarter. Discussion surrounding what resources would be needed to host these monthly |
135 | 164 |
|
136 | 165 | ## Mar 25, 2025 |
|
0 commit comments