---
tags: NumPy, triage
---

# 2024-12-11 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**: Matti, Chuck, Tyler, Sebastian, Inessa, Sayed, Nathan

## Follow up from previous meetings

- Sebastian: Looking into cleaning out buffering (reduce but not just reduce)... The one change, I think is needed is reducing the buffer-size up to half size.
(I think that is fine, since it is unlikely you always get buffer-size sized chunks, since it would require the array to be a multiple of that size...)
- Matti will set up a time to go over it and review together with Sebastian.

## New topics

- Build and upload documentation for 2.2
- Discussion on Slack: https://numpy-team.slack.com/archives/CM8C6PE67/p1733919588780059
- Matti will take a look (done 15.12)

- Should we move to a newer `manylinux_2_28` (RHEL 8 based).
- Amazon support may be one thing to keep in mind (which glibc they support): Amazon linux 2 would not be supported and that is supported until June 25.
- Seems we don't have to worry about Amazon, as it is EOL about the same time as NumPy 2.3 will be released.
- One thing to check when we make this move: can we remove some of the blocklisted trig functions?

## Action items

## 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)