owned this note
owned this note
Published
Linked with GitHub
---
tags: NumPy, triage
---
# 2024-11-13 NumPy triage meeting
- Time: 18:00 (6 pm) UTC
- Join via Zoom: https://numfocus-org.zoom.us/j/82096749952?pwd=MW9oUmtKQ1c3a2gydGk1RTdYUUVXZz09 (To dial in, find your local number: https://numfocus-org.zoom.us/u/kjGWtVx5y)
- [NumPy community events calendar](https://scientific-python.org/calendars)
- [Triage meetings notes archive](https://github.com/numpy/archive/tree/master/triage_meetings)
- [Community meetings notes archive](https://github.com/numpy/archive/tree/main/community_meetings) and [new meetings agenda](https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg)
- [Documentation team meetings notes archive](https://github.com/numpy/archive/tree/main/docs_team_meetings)
**Code of Conduct**
The NumPy Steering Council has made a strong commitment to creating an open, inclusive, and positive community.
All attendees of NumPy community events must adhere to the NumPy Code of Conduct (https://numpy.org/code-of-conduct/).
If you see violations, take a screenshot, intervene in a respectful manner, and report it to the CoC Committee via email. For more information, refer to the Reporting Guidelines section on https://numpy.org/code-of-conduct/.
**Present**: Inessa Pawson, Sayed Adel, Chuck Harris, Sebastian Berg, Maryanne Wachter, Mateusz Sokol, Riley Rockwell, Tyler Reddy
## Follow up from previous meetings
- [name=Adrin] (hopefully this is the right place to put it). It'd be nice if I could get some insight into this issue): https://github.com/numpy/numpy/pull/26018#discussion_r1771824129
- There is not a whole lot to discuss, we need a careful review
- Discussion about OpenBLAS threads (should we increase the threshold when threads are used)?
- We should write a FAQ
- Endorsing SPECs 1, 6, 7, 8
SPEC 1 — Lazy Loading of Submodules and Functions (https://scientific-python.org/specs/spec-0001)
SPEC 6 — Keys to the Castle (https://scientific-python.org/specs/spec-0006)
SPEC 7 — Seeding Pseudo-Random Number Generation (https://scientific-python.org/specs/spec-0007)
SPEC 8 — Securing the Release Process (https://scientific-python.org/specs/spec-0008)
- Action item: open PRs in https://github.com/scientific-python/specs and ask for three steering council members to give a thumbs-up endorsment.
## New topics
- [name=mtsokol] I think it's ready: https://github.com/numpy/numpy/pull/27735
- [name=mtsokol] `__module__` items to clean-up: https://github.com/numpy/numpy/pull/27716 (related comment: https://github.com/pytorch/pytorch/issues/136559#issuecomment-2372364658)
- [name=sayed] loongarch: https://github.com/numpy/numpy/pull/27662
- If we accept this PR which uses Universal Intrinsics, we will make it harder to move to Highway which does not support loongarch. The PR does have CI with QEMU support, which was the minimum request. It seems Highway has no immediate plans to support loongarch.
## Action items
- https://github.com/numpy/numpy/milestone/133
## Backlog
* [PRs and issues labelled with "triage review"](https://github.com/numpy/numpy/labels/triage%20review) (please add)
* [Open PRs - ](https://github.com/numpy/numpy/pulls)- aim to keep below 150
* [Open PRs from first-time contributors](https://github.com/orgs/numpy/projects/5)
* [Inactive PRs](https://github.com/orgs/numpy/projects/6)
---
### Let's connect and keep the conversation going!
Join the NumPy contributor community **Slack workspace**: https://join.slack.com/t/numpy-team/shared_invite/zt-1gokbq56s-bvEpo10Ef7aHbVtVFeZv2w
Sign up to the NumPy **mailing list**: [https://mail.python.org/mailman/listinfo/numpy-discussion](https://mail.python.org/mailman/listinfo/numpy-discussion)
Subscribe to the NumPy **YouTube** channel: https://www.youtube.com/c/NumPy_team
Follow us on **X**: [@numpy_team](https://x.com/numpy_team)
Follow us on **LinkedIn**: https://www.linkedin.com/company/numpy/
#### Presentation topics for NumPy Newcomers’ Hour
To suggest a topic for future presentations, please leave a comment in this tracking issue: https://github.com/numpy/archive/issues/58.
---
Remember to archive this file by committing it to [github.com/numpy/archive/triage_meetings](https://github.com/numpy/archive/tree/main/triage_meetings)