Skip to content

Mention open PR limit #908

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ngoldbaum wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Mention open PR limit #908

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
99c5cf3
Mention open PR limit
ngoldbaum Aug 4, 2026
5e9cb20
Mention the mailing list for the meeting schedule
ngoldbaum Aug 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 13 additions & 5 deletions content/en/contribute.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,11 +19,16 @@ if you prefer to talk privately, contact our community coordinators at
<numpy-team@googlegroups.com> or on [Slack](https://numpy-team.slack.com)
(write <numpy-team@googlegroups.com> for an invite).

We also have a biweekly _community call_, details of which are announced on

@InessaPawson InessaPawson Aug 4, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ngoldbaum The PR looks good overall. My only suggestion would be to keep the mention that community event announcements are also shared on the mailing list. Over the years, I've heard from multiple people that the Scientific Python calendar isn't the most user-friendly, and folks still rely on the mailing list to learn or be reminded about upcoming NumPy community events.

@ngoldbaum ngoldbaum Aug 4, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does the latest push look ok?

the [mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion).
You are very welcome to join.
If you are new to contributing to open source, we also highly recommend reading
[this guide](https://opensource.guide/how-to-contribute/).
We also have _community_ and _triage_ meetings, alternating weekly on
Wednesdays; see the [community
calendar](https://scientific-python.org/calendars/) for times. We also announce
the meetings on the [mailing
list](https://mail.python.org/mailman/listinfo/numpy-discussion). You are very
welcome to join.

If you are new to contributing to open source, we
also highly recommend reading [this
guide](https://opensource.guide/how-to-contribute/).

Our community aspires to treat everyone equally and to value all
contributions. We have a [Code of Conduct](/code-of-conduct) to foster an open
Expand All @@ -38,6 +43,9 @@ For a visual guide on how to contribute to NumPy, check out this [comic](https:/
Programmers, this
[guide](https://numpy.org/devdocs/dev/index.html#development-process-summary)
explains how to contribute to the NumPy codebase.
Note that non-maintainers may only have one non-draft pull request open for
review at a time. Come introduce yourself at a community or triage meeting
to be added to the exception list for the one-PR-at-a-time policy.
<br>Check out also our [YouTube channel](https://www.youtube.com/playlist?list=PLCK6zCrcN3GXBUUzDr9L4__LnXZVtaIzS) for additional advice.

### Reviewing pull requests
Expand Down