Deploying to main from @ numpy/numpy.org@1790faa 🚀

Author: InessaPawson

contribute/index.html

@@ -20,15 +20,21 @@
 issue).</p><p>Those are our preferred channels (open source is open by nature), but
 if you prefer to talk privately, contact our community coordinators at
 <a href=mailto:numpy-team@googlegroups.com>numpy-team@googlegroups.com</a> or on <a href=https://numpy-team.slack.com>Slack</a>
-(write <a href=mailto:numpy-team@googlegroups.com>numpy-team@googlegroups.com</a> for an invite).</p><p>We also have a biweekly <em>community call</em>, details of which are announced on
-the <a href=https://mail.python.org/mailman/listinfo/numpy-discussion>mailing list</a>.
-You are very welcome to join.
-If you are new to contributing to open source, we also highly recommend reading
-<a href=https://opensource.guide/how-to-contribute/>this guide</a>.</p><p>Our community aspires to treat everyone equally and to value all
+(write <a href=mailto:numpy-team@googlegroups.com>numpy-team@googlegroups.com</a> for an invite).</p><p>We also have <em>community</em> and <em>triage</em> meetings, alternating weekly on
+Wednesdays; see the <a href=https://scientific-python.org/calendars/>community
+calendar</a> for times. We also announce
+the meetings on the <a href=https://mail.python.org/mailman/listinfo/numpy-discussion>mailing
+list</a>. You are very
+welcome to join.</p><p>If you are new to contributing to open source, we
+also highly recommend reading <a href=https://opensource.guide/how-to-contribute/>this
+guide</a>.</p><p>Our community aspires to treat everyone equally and to value all
 contributions. We have a <a href=/code-of-conduct/>Code of Conduct</a> to foster an open
 and welcoming environment.</p><p>For a visual guide on how to contribute to NumPy, check out this <a href=https://heyzine.com/flip-book/3e66a13901.html>comic</a>.</p><div class=comic><a href=https://heyzine.com/flip-book/3e66a13901.html><img src=/images/content_images/numpy-comic.png alt="NumPy Contributor comic book cover"></a></div><style>.comic img{max-width:20%}</style><h3 id=writing-code>Writing code<a class=headerlink href=#writing-code title="Link to this heading">#</a></h3><p>Programmers, this
 <a href=https://numpy.org/devdocs/dev/index.html#development-process-summary>guide</a>
-explains how to contribute to the NumPy codebase.<br>Check out also our <a href="https://www.youtube.com/playlist?list=PLCK6zCrcN3GXBUUzDr9L4__LnXZVtaIzS">YouTube channel</a> for additional advice.</p><h3 id=reviewing-pull-requests>Reviewing pull requests<a class=headerlink href=#reviewing-pull-requests title="Link to this heading">#</a></h3><p>The project has more than 250 open pull requests &ndash; meaning many potential
+explains how to contribute to the NumPy codebase.
+Note that non-maintainers may only have two 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 two-PRs-at-a-time policy.<br>Check out also our <a href="https://www.youtube.com/playlist?list=PLCK6zCrcN3GXBUUzDr9L4__LnXZVtaIzS">YouTube channel</a> for additional advice.</p><h3 id=reviewing-pull-requests>Reviewing pull requests<a class=headerlink href=#reviewing-pull-requests title="Link to this heading">#</a></h3><p>The project has more than 250 open pull requests &ndash; meaning many potential
 improvements and many open-source contributors waiting for feedback. If you&rsquo;re
 a developer who knows NumPy, you can help even if you&rsquo;re not familiar with the
 codebase. You can:</p><ul><li>summarize a long-running discussion</li><li>triage documentation PRs</li><li>test proposed changes</li></ul><h3 id=developing-educational-materials>Developing educational materials<a class=headerlink href=#developing-educational-materials title="Link to this heading">#</a></h3><p>NumPy&rsquo;s <a href=https://numpy.org/devdocs>User Guide</a> is undergoing rehabilitation.