---
tags: NumPy
---

# 2025-05-19 NumPy Documentation Team meeting

- Time: 7 pm UTC
- Join via Zoom: https://numfocus-org.zoom.us/j/85016474448?pwd=TWEvaWJ1SklyVEpwNXUrcHV1YmFJQT09 (To dial in, find your local number: https://numfocus-org.zoom.us/u/kbRSNdYfoZ)
- [NumPy community events calendar](https://scientific-python.org/calendars/)
- [Documentation issues](https://github.com/numpy/numpy/labels/04%20-%20Documentation)
- [Documentation brainstorming document](https://hackmd.io/RdtnQZpLRZqgNRe4gaJ0SA) - anything that is not yet ready for an issue or PR or needs a discussion
- [Documentation team meetings notes archive](https://github.com/numpy/archive/tree/main/docs_team_meetings)
- [Community meetings notes archive](https://github.com/numpy/archive/tree/main/community_meetings)
- [Triage meetings notes archive](https://github.com/numpy/archive/tree/master/triage_meetings)
- Next meeting: TBD

### Useful links

- Getting started with building documentation: https://numpy.org/devdocs/dev/howto_build_docs.html
- How to contribute to the NumPy documentation: https://numpy.org/devdocs/dev/howto-docs.html

### Topics Discussed
- PDF version of NumPy Documentation (see some details under New Topics below)
- Leveraging Python Conferences to help attendeed get onboarded to NumPy. Handouts needed at such events.
- Encouraging students and other NumPy users to consider contributing examples as tutorials. See https://numpy.org/numpy-tutorials/

### Code of Conduct

We want to take a moment to remind you that this meeting is meant to be welcoming and inclusive. It's important for us to have a healthy community. Like all NumPy spaces, and everyone participating in them, this meeting will follow our [Code of Conduct](https://numpy.org/code-of-conduct/). If you haven't read it yet, please take some time to do so later on as it already applies to you. For now, in short, please be kind and generous towards one another.

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:** Ben Woodruff

**Notes taken by:**

## Standing topics

- [name=inessa] Presentation topics for NumPy Newcomers’ Hour
To suggest a topic for future presentations, leave a comment in this tracking issue: https://github.com/numpy/archive/issues/58.
- Short form content?

- [name=Inessa & Melissa] [Documentation user stories](https://github.com/numpy/numpy/issues/22089)
*Feel free to add yours!*

- Inessa: issues related to the NumPy educational content:
https://github.com/numpy/archive/issues/55
If you’d like to work on any of them, leave a comment on GitHub (below the relevant issue).

- Tracking inactive PRs: https://github.com/orgs/numpy/projects/6
(help with triaging is welcome!)

## Follow-up from last meeting / discussions

- Possible small development grant? It could be nice to have someone dedicated to finishing the Doxygen integration and updating the C docs. Ref: [DOC: Questions Regarding C-API Documentation Status and Maintenance](https://github.com/numpy/numpy/issues/27576)
- We have an interested contributor. Has to be discussed at the community meeting for further plans.

- [Google Season of Docs has shut down its program.](https://developers.google.com/season-of-docs/)

## New topics

### 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**: mail.python.org/mailman/listinfo/numpy-discussion

Subscribe to the NumPy **YouTube** channel: https://www.youtube.com/c/NumPy_team

Follow us on **Twitter**: [@numpy_team](https://twitter.com/numpy_team)

Follow us on **LinkedIn**: https://www.linkedin.com/company/numpy/

---
Remember to archive this file by committing it to
[https://github.com/numpy/archive/tree/main/docs_team_meetings](https://github.com/numpy/archive/tree/main/docs_team_meetings)