|
| 1 | +--- |
| 2 | +tags: NumPy |
| 3 | +--- |
| 4 | + |
| 5 | +# 2019-08-14 NumPy Development Meeting |
| 6 | + |
| 7 | +- Time: 11am Pacific Time |
| 8 | +- Join via Zoom at https://berkeley.zoom.us/j/762261535 |
| 9 | +- [Trello workboard](https://trello.com/b/Azg4fYZH/numpy-at-bids) |
| 10 | +- [Previous meetings](https://github.com/BIDS-numpy/docs/tree/master/status_meetings) |
| 11 | + |
| 12 | +**Present:** Tyler, Chuck, Thomas Caswell, Warren, Ralf, Inessa, Matti, Zijie Poh, Stéfan, Kriti, Peter Entschev |
| 13 | + |
| 14 | + |
| 15 | +## Follow-up from last meeting / discussions |
| 16 | + |
| 17 | +- Proposal for dropping older Python versions [NEP 29](https://github.com/numpy/numpy/pull/14086/files) |
| 18 | + - We need some data (Python 3.5 downloads). Preliminary analysis at [this repo](https://github.com/matthew-brett/pypi-by-distro). See results at end of [this notebook](https://github.com/matthew-brett/pypi-by-distro/blob/master/analyze_pypi_downloads.ipynb). |
| 19 | + - Platforms like Raspberry or systems like PyPy |
| 20 | + - Maybe probably target things like Ubuntu LTS? |
| 21 | + - The people involved in the discussion are not those affected by it. (we may force users to Anaconda). |
| 22 | + - NEP could have options: Projects could decide how fast they move. |
| 23 | + - After discussion we reached a recommendation for a minimum of 36 months and/or 2 version of cpython (the longer of the two) |
| 24 | + |
| 25 | +- NumPy Community Survey: |
| 26 | + - Objective: To engage all NumPy stakeholders and the broader Python community in a conversation that will help to guide decision-making around the project. |
| 27 | + - Distribution channels: PyData.org (100k+ members), social media. |
| 28 | + - To encourage participation in the survey perhaps we could offer to share the survey results report with the participants first, before releasing it into public domain. |
| 29 | + - The survey should have up to 50 questions, mainly close-ended to allow easy completion and processing. |
| 30 | + - Inessa is going to send out an announcement about the planned survey via the NumPy mailing list, and create a repo on GitHub to collaborate on this project. |
| 31 | + - Do we want various languages? Maybe translate the survey itself, but ask for comments in English. |
| 32 | + |
| 33 | + |
| 34 | +- GSoD kickoff call summary |
| 35 | + - https://hackmd.io/oB_boakvRqKR-_2jRV-Qjg |
| 36 | + |
| 37 | +- Duckarray [NEP](https://github.com/numpy/numpy/blob/master/doc/neps/nep-0030-duck-array-protocol.rst) |
| 38 | + - Expand the Motivation (potential users) a bit. |
| 39 | + - Some bikeshedding on naming seems inevitable. |
| 40 | + |
| 41 | + |
| 42 | +# Topics |
| 43 | + |
| 44 | +- Welcoming Warren Weckesser |
| 45 | + - Warren @WarrenWeckesser is joining the BIDS team, will be working full-time on NumPy. Welcome, Warren! |
| 46 | + - GitHub team membership |
| 47 | +- Monitoring of issues / PRs |
| 48 | + - Still a lot of low-hanging triaging fruit; Ralf recently closed 130 on SciPy in a few hours, team did 200 in total. About 75% of issues that haven't been commented on in 3 years could be closed. |
| 49 | + - [Helpful queries on GitHub](https://github.com/numpy/numpy/wiki/Github-Queries) — feel free to update |
| 50 | + - **DONE** Add a [label](https://github.com/numpy/numpy/labels) for [question](https://github.com/numpy/numpy/labels/question), [installation](https://github.com/numpy/numpy/labels/installation) |
| 51 | + - **TODO** Remove difficulty labels, tag easy ones with `good first issue` which is recognized by GitHub UI |
| 52 | + |
| 53 | +## Additional Details |
| 54 | + |
| 55 | +- Matti |
| 56 | + - We no longer are tied to http://scipy.org, we should always refer to numpy.org and numpy.org/doc |
| 57 | + |
| 58 | +- Sebastian |
| 59 | + - Draft starts (prototyping): https://hackmd.io/kxuh15QGSjueEKft5SaMug, https://hackmd.io/y7ghitUtRQaMyaHFGe-ueQ |
| 60 | + - Towncrier |
| 61 | + |
| 62 | +- Warren |
| 63 | + - Contribute some time to reviewing PRs |
| 64 | + - Catch up on Sebastian's NEP / dtype work |
| 65 | + - Identify project to work on over next few months |
| 66 | + |
0 commit comments