deploy: 245fcb3

_sources/software_steering_council.md

@@ -16,7 +16,7 @@ The SSC is responsible for the following:
 - Stewarding the JEP process to ensure that it is inclusive and participatory, and solicits feedback from the right stakeholders. As a starting point, [the NumFOCUS DISCOVER Cookbook](https://github.com/numfocus/DISCOVER-Cookbook) may offer some useful starting pointers.
 - Making decisions on JEPs after receiving community feedback (JEPs are the mechanism for elevating any software decision/idea up to the broader Project, while individual Subprojects can make decisions within their scope via their regular mechanisms).
 - Owning, managing and implementing the Jupyter Incubation process (https://github.com/jupyter-incubator).
-- Owning, managing and implementing the Jupyter Attic process (https://github.com/jupyter-attic).
+- Owning, managing and implementing the Jupyter Attic process (https://github.com/orgs/jupyter/repositories?type=source&q=archived%3Atrue).
 - Stewarding discussions and activities beyond JEPs that involve cross-cutting concerns, standards, protocols and other architectural issues that impact the entire project.
 - Owning and managing anything related to security vulnerabilities across the project, including the Jupyter security lists, any private security repositories, etc.
 - Voting to accept Working Groups nominated by the Executive Council (EC) to have a representative on the SSC.

software_steering_council.html

@@ -403,7 +403,7 @@ <h3>Sole responsibilities<a class="headerlink" href="#sole-responsibilities" tit
 <li><p>Stewarding the JEP process to ensure that it is inclusive and participatory, and solicits feedback from the right stakeholders. As a starting point, <a class="reference external" href="https://github.com/numfocus/DISCOVER-Cookbook">the NumFOCUS DISCOVER Cookbook</a> may offer some useful starting pointers.</p></li>
 <li><p>Making decisions on JEPs after receiving community feedback (JEPs are the mechanism for elevating any software decision/idea up to the broader Project, while individual Subprojects can make decisions within their scope via their regular mechanisms).</p></li>
 <li><p>Owning, managing and implementing the Jupyter Incubation process (<a class="github reference external" href="https://github.com/jupyter-incubator">jupyter-incubator</a>).</p></li>
-<li><p>Owning, managing and implementing the Jupyter Attic process (<a class="github reference external" href="https://github.com/jupyter-attic">jupyter-attic</a>).</p></li>
+<li><p>Owning, managing and implementing the Jupyter Attic process (<a class="reference external" href="https://github.com/orgs/jupyter/repositories?type=source&amp;amp;q=archived%3Atrue">https://github.com/orgs/jupyter/repositories?type=source&amp;q=archived%3Atrue</a>).</p></li>
 <li><p>Stewarding discussions and activities beyond JEPs that involve cross-cutting concerns, standards, protocols and other architectural issues that impact the entire project.</p></li>
 <li><p>Owning and managing anything related to security vulnerabilities across the project, including the Jupyter security lists, any private security repositories, etc.</p></li>
 <li><p>Voting to accept Working Groups nominated by the Executive Council (EC) to have a representative on the SSC.</p></li>