deploy: ec894af

_sources/community/github/our-repositories.md.txt

@@ -13,6 +13,9 @@ The software-review repository is where community package submissions are
 peer-reviewed. All submissions are made through GitHub Issues. [Learn more
 about our peer review process here.](https://www.pyopensci.org/software-peer-review/)
 
+Teams with access to this repository:
+* [the pyOpenSci Editorial Board](https://github.com/orgs/pyOpenSci/teams/editorial-board)
+
 :::{important}
 Important: If a pyOpenSci core member identifies an issue with the review
 submission template, consult both the editorial team and core team before
@@ -29,19 +32,30 @@ peer review triage team as they manage our open peer review process. It also
 details our peer review policies, partnerships, and the templates used in the
 review process.
 
+Individuals and teams with access to this repository include:
+* [the pyOpenSci Editorial Board](https://github.com/orgs/pyOpenSci/teams/editorial-board)
+* [the pyOpenSci Repository Maintainers team](https://github.com/orgs/pyOpenSci/teams/pyos-repo-maintainers).
+
 ## Python-package-guide repository
 
 The [python-package-guide
 repository](https://www.pyopensci.org/python-package-guide/) contains our
 community-developed guidelines and tutorials on Python packaging. These
 resources are beginner-friendly and reflect Python packaging best practices.
 
+Teams with access to this repository:
+* [the pyOpenSci Packaging Council](https://github.com/orgs/pyOpenSci/teams/packaging-council)
+* [the pyOpenSci Repository Maintainers team](https://github.com/orgs/pyOpenSci/teams/pyos-repo-maintainers)
+
 ## [pyosMeta repository](https://github.com/pyOpenSci/pyosMeta)
 
 The pyosMeta repository contains a Python package published on PyPI that we use
 to track our package review and contributor data. This data is used in a GitHub
 action to update our website.
 
+Teams with access to this repository:
+* [the pyOpenSci Repository Maintainers team](https://github.com/orgs/pyOpenSci/teams/pyos-repo-maintainers)
+
 :::{todo}
 Add more information about the contributor data workflow ...
 :::
@@ -57,6 +71,10 @@ automatically using a GitHub action workflow that is supported by the pyosMeta
 Python package discussed above. The workflow runs every other week but can be
 triggered manually as a **workflow dispatch**.
 
+Teams with access to this repository:
+* [the pyOpenSci Editorial Board](https://github.com/orgs/pyOpenSci/teams/editorial-board)
+* [the pyOpenSci Repository Maintainers team](https://github.com/orgs/pyOpenSci/teams/pyos-repo-maintainers)
+
 ### Critical CI workflows in this repository
 
 The [contributor workflow
@@ -109,16 +127,36 @@ of our repositories that use the theme.
 Creating a theme was inspired by the
 [2i2c Sphinx theme](https://sphinx-2i2c-theme.readthedocs.io/en/latest/).
 
+Teams with access to this repository:
+* [the pyOpenSci Repository Maintainers team](https://github.com/orgs/pyOpenSci/teams/pyos-repo-maintainers)
+
 ## [Handbook repository](https://github.com/pyOpenSci/handbook)
 
 **Platform:** Sphinx book running the `pydata_sphinx_theme`
 
 This is where we store our organization governance, code of conduct, and
 processes around how we operate as an organization.
 
+The [pyOpenSci Executive Council](https://www.pyopensci.org/our-community/index.html#executive-council-leadership--staff) has access to this repo.
+
 ## [pyosPackage repository](https://github.com/pyOpenSci/pyosPackage)
 
 The pyosPackage repo contains an example pure-Python package that complements
 our package guide & tutorials. We will build this package example out over time
 for folks that just want to see a working package without creating one
 themselves.
+
+Teams with access to this repository:
+* [the pyOpenSci Packaging Council](https://github.com/orgs/pyOpenSci/teams/packaging-council).
+
+## [peer-review-metrics repository](https://github.com/pyOpenSci/peer-review-metrics)
+
+The pyOpenSci peer review metrics repository contains the code for a dashboard created using [MyST Markdown](https://mystmd.org/). Myst-md is a community developed tool that makes it easier for scientists to create fully reproducible (and interactive) workflows and reports that are easily shared.
+
+Only pyOpenSci GitHub organization admins have direct access to modify this repository.
+
+## [lessons repository](https://github.com/pyOpenSci/lessons)
+
+pyOpenSci is devoted to building diverse, supportive community around the Python open source tools that drive open science. The lessons repository contains the source files for all of the [pyOpenSci tutorials](https://github.com/pyOpenSci/lessons).
+
+The [pyOpenSci Lesson Development Team](https://github.com/orgs/pyOpenSci/teams/lesson-development) has access to this repo.

community/github/our-repositories.html

@@ -527,6 +527,10 @@ <h2><a class="reference external" href="https://www.pyopensci.org/software-peer-
 <p>The software-review repository is where community package submissions are
 peer-reviewed. All submissions are made through GitHub Issues. <a class="reference external" href="https://www.pyopensci.org/software-peer-review/">Learn more
 about our peer review process here.</a></p>
+<p>Teams with access to this repository:</p>
+<ul class="simple">
+<li><p><a class="reference external" href="https://github.com/orgs/pyOpenSci/teams/editorial-board">the pyOpenSci Editorial Board</a></p></li>
+</ul>
 <div class="admonition important">
 <p class="admonition-title">Important</p>
 <p>Important: If a pyOpenSci core member identifies an issue with the review
@@ -543,19 +547,33 @@ <h2>Software-peer-review guidebook repository<a class="headerlink" href="#softwa
 peer review triage team as they manage our open peer review process. It also
 details our peer review policies, partnerships, and the templates used in the
 review process.</p>
+<p>Individuals and teams with access to this repository include:</p>
+<ul class="simple">
+<li><p><a class="reference external" href="https://github.com/orgs/pyOpenSci/teams/editorial-board">the pyOpenSci Editorial Board</a></p></li>
+<li><p><a class="reference external" href="https://github.com/orgs/pyOpenSci/teams/pyos-repo-maintainers">the pyOpenSci Repository Maintainers team</a>.</p></li>
+</ul>
 </section>
 <section id="python-package-guide-repository">
 <h2>Python-package-guide repository<a class="headerlink" href="#python-package-guide-repository" title="Link to this heading">#</a></h2>
 <p>The <a class="reference external" href="https://www.pyopensci.org/python-package-guide/">python-package-guide
 repository</a> contains our
 community-developed guidelines and tutorials on Python packaging. These
 resources are beginner-friendly and reflect Python packaging best practices.</p>
+<p>Teams with access to this repository:</p>
+<ul class="simple">
+<li><p><a class="reference external" href="https://github.com/orgs/pyOpenSci/teams/packaging-council">the pyOpenSci Packaging Council</a></p></li>
+<li><p><a class="reference external" href="https://github.com/orgs/pyOpenSci/teams/pyos-repo-maintainers">the pyOpenSci Repository Maintainers team</a></p></li>
+</ul>
 </section>
 <section id="pyosmeta-repository">
 <h2><a class="reference external" href="https://github.com/pyOpenSci/pyosMeta">pyosMeta repository</a><a class="headerlink" href="#pyosmeta-repository" title="Link to this heading">#</a></h2>
 <p>The pyosMeta repository contains a Python package published on PyPI that we use
 to track our package review and contributor data. This data is used in a GitHub
 action to update our website.</p>
+<p>Teams with access to this repository:</p>
+<ul class="simple">
+<li><p><a class="reference external" href="https://github.com/orgs/pyOpenSci/teams/pyos-repo-maintainers">the pyOpenSci Repository Maintainers team</a></p></li>
+</ul>
 </section>
 <section id="pyopensci-github-io-repository">
 <h2><a class="reference external" href="https://github.com/pyOpenSci/pyopensci.github.io">pyopensci.github.io repository</a><a class="headerlink" href="#pyopensci-github-io-repository" title="Link to this heading">#</a></h2>
@@ -567,6 +585,11 @@ <h2><a class="reference external" href="https://github.com/pyOpenSci/pyopensci.g
 automatically using a GitHub action workflow that is supported by the pyosMeta
 Python package discussed above. The workflow runs every other week but can be
 triggered manually as a <strong>workflow dispatch</strong>.</p>
+<p>Teams with access to this repository:</p>
+<ul class="simple">
+<li><p><a class="reference external" href="https://github.com/orgs/pyOpenSci/teams/editorial-board">the pyOpenSci Editorial Board</a></p></li>
+<li><p><a class="reference external" href="https://github.com/orgs/pyOpenSci/teams/pyos-repo-maintainers">the pyOpenSci Repository Maintainers team</a></p></li>
+</ul>
 <section id="critical-ci-workflows-in-this-repository">
 <h3>Critical CI workflows in this repository<a class="headerlink" href="#critical-ci-workflows-in-this-repository" title="Link to this heading">#</a></h3>
 <p>The <a class="reference external" href="https://github.com/pyOpenSci/pyopensci.github.io/blob/main/.github/workflows/update-contribs-reviews.yml">contributor workflow
@@ -613,19 +636,38 @@ <h2><a class="reference external" href="https://github.com/pyOpenSci/pyos-sphinx
 of our repositories that use the theme.</p>
 <p>Creating a theme was inspired by the
 <a class="reference external" href="https://sphinx-2i2c-theme.readthedocs.io/en/latest/">2i2c Sphinx theme</a>.</p>
+<p>Teams with access to this repository:</p>
+<ul class="simple">
+<li><p><a class="reference external" href="https://github.com/orgs/pyOpenSci/teams/pyos-repo-maintainers">the pyOpenSci Repository Maintainers team</a></p></li>
+</ul>
 </section>
 <section id="handbook-repository">
 <h2><a class="reference external" href="https://github.com/pyOpenSci/handbook">Handbook repository</a><a class="headerlink" href="#handbook-repository" title="Link to this heading">#</a></h2>
 <p><strong>Platform:</strong> Sphinx book running the <code class="docutils literal notranslate"><span class="pre">pydata_sphinx_theme</span></code></p>
 <p>This is where we store our organization governance, code of conduct, and
 processes around how we operate as an organization.</p>
+<p>The <a class="reference external" href="https://www.pyopensci.org/our-community/index.html#executive-council-leadership--staff">pyOpenSci Executive Council</a> has access to this repo.</p>
 </section>
 <section id="pyospackage-repository">
 <h2><a class="reference external" href="https://github.com/pyOpenSci/pyosPackage">pyosPackage repository</a><a class="headerlink" href="#pyospackage-repository" title="Link to this heading">#</a></h2>
 <p>The pyosPackage repo contains an example pure-Python package that complements
 our package guide &amp; tutorials. We will build this package example out over time
 for folks that just want to see a working package without creating one
 themselves.</p>
+<p>Teams with access to this repository:</p>
+<ul class="simple">
+<li><p><a class="reference external" href="https://github.com/orgs/pyOpenSci/teams/packaging-council">the pyOpenSci Packaging Council</a>.</p></li>
+</ul>
+</section>
+<section id="peer-review-metrics-repository">
+<h2><a class="reference external" href="https://github.com/pyOpenSci/peer-review-metrics">peer-review-metrics repository</a><a class="headerlink" href="#peer-review-metrics-repository" title="Link to this heading">#</a></h2>
+<p>The pyOpenSci peer review metrics repository contains the code for a dashboard created using <a class="reference external" href="https://mystmd.org/">MyST Markdown</a>. Myst-md is a community developed tool that makes it easier for scientists to create fully reproducible (and interactive) workflows and reports that are easily shared.</p>
+<p>Only pyOpenSci GitHub organization admins have direct access to modify this repository.</p>
+</section>
+<section id="lessons-repository">
+<h2><a class="reference external" href="https://github.com/pyOpenSci/lessons">lessons repository</a><a class="headerlink" href="#lessons-repository" title="Link to this heading">#</a></h2>
+<p>pyOpenSci is devoted to building diverse, supportive community around the Python open source tools that drive open science. The lessons repository contains the source files for all of the <a class="reference external" href="https://github.com/pyOpenSci/lessons">pyOpenSci tutorials</a>.</p>
+<p>The <a class="reference external" href="https://github.com/orgs/pyOpenSci/teams/lesson-development">pyOpenSci Lesson Development Team</a> has access to this repo.</p>
 </section>
 </section>
 
@@ -688,6 +730,8 @@ <h2><a class="reference external" href="https://github.com/pyOpenSci/pyosPackage
 <li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#pyopensci-sphinx-theme">pyOpenSci Sphinx theme</a></li>
 <li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#handbook-repository">Handbook repository</a></li>
 <li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#pyospackage-repository">pyosPackage repository</a></li>
+<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#peer-review-metrics-repository">peer-review-metrics repository</a></li>
+<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#lessons-repository">lessons repository</a></li>
 </ul>
   </nav></div>
 

community/index.html

@@ -558,6 +558,8 @@ <h1>Community Handbook<a class="headerlink" href="#community-handbook" title="Li
 <li class="toctree-l2"><a class="reference internal" href="github/our-repositories.html#pyopensci-sphinx-theme">pyOpenSci Sphinx theme</a></li>
 <li class="toctree-l2"><a class="reference internal" href="github/our-repositories.html#handbook-repository">Handbook repository</a></li>
 <li class="toctree-l2"><a class="reference internal" href="github/our-repositories.html#pyospackage-repository">pyosPackage repository</a></li>
+<li class="toctree-l2"><a class="reference internal" href="github/our-repositories.html#peer-review-metrics-repository">peer-review-metrics repository</a></li>
+<li class="toctree-l2"><a class="reference internal" href="github/our-repositories.html#lessons-repository">lessons repository</a></li>
 </ul>
 </li>
 <li class="toctree-l1"><a class="reference internal" href="github/issues.html">GitHub Issue Guidelines</a><ul>