owned this note
owned this note
Published
Linked with GitHub
---
tags: NumPy
---
# 2024-04-08 NumPy Documentation Team meeting
- Time: 11 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: 2024-04-22 @ 11PM UTC
### 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
### 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:** Mukulika, Mars
**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
## New topics
- GSOD 2024 proposal submitted!
- [Timeline](https://developers.google.com/season-of-docs/docs/timeline)
- Find out if accepted on April 10, 18:00 UTC
- [2023 Case study](https://github.com/numpy/numpy/wiki/Google-Season-of-Docs-2023:-NumPy-case-study)
- [2024 Proposal](https://github.com/numpy/numpy/wiki/Google-Season-of-Docs-2024:-Project-Proposal)
- Sketches of last two pages of "How to Contribute to NumPy comics"
- [Link to pages 12,13,14,15](https://raw.githubusercontent.com/MarsBarLee/gsod-numpy-2023/main/Last%206%20pages.png)
- [Link to page 16, 17](https://github.com/MarsBarLee/gsod-numpy-2023/blob/main/16,%2017.png?raw=true)
- I think page 17 is a bit busy, but I was trying to fit the last parts of the script into the last page.
- Half of page 18/back cover as ending, acts as a summary of comic, pointing out to NumPy Slack, mailing list and community call, along with credits
- Gives more space for content on page 17, to take up space fully without feeling cramped
- Create page 18/back cover
- [Script from last two pages, where it gets busy](https://docs.google.com/document/d/1fjLTDqSkcKMxo8oSTRThllBFpjo5rXS9/edit#bookmark=id.4d34og8)
- Does not include credits: perhaps text instead of illustration of short on time.
- Comments on overview: happy how translated scrpit to visuals, accruate. Like how story ties together, leave with tips on how to interact with open source communities
- POV changes, from PR maker to maintainer, humanize process
- Collaborate with future editions of NumPy Community Survey on effectiveness of comics
- (Mukulika) Rerun poll for docs meeting times
---
### 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)