---
tags: NumPy, triage
---

# 2020-02-24 NumPy Development Meeting -- Triage

Note: we alternate between [community meetings](https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg) and triage meetings.

- Time: 11am Pacific Time
- Join via Zoom at https://berkeley.zoom.us/j/762261535 (or [dial-in](https://berkeley.zoom.us/u/aC3ENhycM))
- [Trello workboard](https://trello.com/b/Azg4fYZH/numpy-at-bids)
- [Previous community meetings](https://github.com/numpy/archive/tree/master/status_meetings)
- [Previous triage meetings](https://github.com/numpy/archive/tree/master/triage_meetings)

**Present:** Chuck, Matti, Ross, Sebastian

## Triage

- [PRs and issues labelled with "Triage-Review"](https://github.com/numpy/numpy/labels/Triage-review) (0 open, please add)

- [PRs and issues labeled with "needs decision"](https://github.com/numpy/numpy/labels/54%20-%20Needs%20decision) (50 open)

- [Open PRs (>250 open)](https://github.com/numpy/numpy/pulls) can we get this below 200?

- Ross' list of cross-referenced issues: https://rossbar.github.io/github_graphql/index.html

## Topics

- `numpy.lib` namespace?
- The `from numpy.lib import *` is probably not important to keep around.
- `np.lib.stride_tricks.broadcast_to` will also be hidden/go away?
- Lets just start with cleaning it up a bit for now.

- pnumpy is getting some use

- new manylinux is going up, which may allow us to drop some of our blocklist glibc.

- M1 status:

- NumPy 1.20.2 release end of the month.

- Lets try to triage next week: Label accordingly!

---

Please remember to archive this file and commit it to github.com/numpy/archive