deploy: ac67c1e

_sources/how-to/editor-in-chief-guide.md.txt

@@ -17,10 +17,10 @@ to support finding a new EiC.
 - Raises scope/overlap issue with all editors if they see an ambiguous submission.
 This may also be done by handling editors if appropriate (see note below). If
 the scope of a package is in question, the EiC should post to the pyOpenSci
-Slack `software-review` channel, tagging all editors.
+Slack `#software-review` channel, tagging all editors.
 - Assigns package submissions to other editors to handle. Assigning may be based upon domain background or just who has bandwidth to lead the review. The editor in chief can assign packages to themself for review.
 - Responds to pre-submission inquiries posted to the software-review repository
-and similarly pings editors in the `software-review` Slack channel if discussion
+and similarly pings editors in the `#software-review` Slack channel if discussion
 is needed. Any editor should feel free to communicate with package authors as it
 makes sense. See [this section](#responding-to-out-of-scope-submissions) about
 how to respond to out-of-scope (pre-) submissions.
@@ -40,7 +40,7 @@ the scope and readiness of a package to be reviewed, they may opt to assign an e
 
 When a new package is submitted for review, the Editor in Chief will:
 
-### 1. ✔️ Tag the issue with `1/editor-checks` tag in GitHub
+### 1. ✔️ Tag the issue with `0/pre-review-checks` tag in GitHub
 
 ### 2. ✔️ Add the editor checks to the issue
 
@@ -86,11 +86,11 @@ information to stay in touch about package maintenance. We also
 want to track their experience with our review process and
 organization.
 
-### 4. ✔️ Assign an editor to the issue to manage the rest of the review
+### 4. ✔️ Assign an editor to the issue to manage the rest of the review and tag the issue with the `1/editor-assigned` tag in GitHub
 
 Once the package initial checks are complete, and it is determined that
 the package is in scope for pyOpenSci review, the Editor in Chief will assign an
-editor to the review issue.
+editor to the review issue and add the `1/editor-assigned` tag in GitHub.
 This may involve finding a new (guest) editor
 as described in the [onboarding guide](onboarding-guide.md).
 If you as Editor in Chief do recruit a new editor,

how-to/editor-in-chief-guide.html

@@ -522,10 +522,10 @@ <h3>The Editor in Chief fulfills the following roles:<a class="headerlink" href=
 <li><p>Raises scope/overlap issue with all editors if they see an ambiguous submission.
 This may also be done by handling editors if appropriate (see note below). If
 the scope of a package is in question, the EiC should post to the pyOpenSci
-Slack <code class="docutils literal notranslate"><span class="pre">software-review</span></code> channel, tagging all editors.</p></li>
+Slack <code class="docutils literal notranslate"><span class="pre">#software-review</span></code> channel, tagging all editors.</p></li>
 <li><p>Assigns package submissions to other editors to handle. Assigning may be based upon domain background or just who has bandwidth to lead the review. The editor in chief can assign packages to themself for review.</p></li>
 <li><p>Responds to pre-submission inquiries posted to the software-review repository
-and similarly pings editors in the <code class="docutils literal notranslate"><span class="pre">software-review</span></code> Slack channel if discussion
+and similarly pings editors in the <code class="docutils literal notranslate"><span class="pre">#software-review</span></code> Slack channel if discussion
 is needed. Any editor should feel free to communicate with package authors as it
 makes sense. See <a class="reference internal" href="#responding-to-out-of-scope-submissions">this section</a> about
 how to respond to out-of-scope (pre-) submissions.</p></li>
@@ -545,8 +545,8 @@ <h3>The Editor in Chief fulfills the following roles:<a class="headerlink" href=
 <section id="editor-in-chief-checklist">
 <h2>Editor in Chief checklist<a class="headerlink" href="#editor-in-chief-checklist" title="Link to this heading">#</a></h2>
 <p>When a new package is submitted for review, the Editor in Chief will:</p>
-<section id="tag-the-issue-with-1-editor-checks-tag-in-github">
-<h3>1. ✔️ Tag the issue with <code class="docutils literal notranslate"><span class="pre">1/editor-checks</span></code> tag in GitHub<a class="headerlink" href="#tag-the-issue-with-1-editor-checks-tag-in-github" title="Link to this heading">#</a></h3>
+<section id="tag-the-issue-with-0-pre-review-checks-tag-in-github">
+<h3>1. ✔️ Tag the issue with <code class="docutils literal notranslate"><span class="pre">0/pre-review-checks</span></code> tag in GitHub<a class="headerlink" href="#tag-the-issue-with-0-pre-review-checks-tag-in-github" title="Link to this heading">#</a></h3>
 </section>
 <section id="add-the-editor-checks-to-the-issue">
 <h3>2. ✔️ Add the editor checks to the issue<a class="headerlink" href="#add-the-editor-checks-to-the-issue" title="Link to this heading">#</a></h3>
@@ -629,11 +629,11 @@ <h3>3. ✔️ Ensure that the package onboarding survey is filled out.<a class="
 want to track their experience with our review process and
 organization.</p>
 </section>
-<section id="assign-an-editor-to-the-issue-to-manage-the-rest-of-the-review">
-<h3>4. ✔️ Assign an editor to the issue to manage the rest of the review<a class="headerlink" href="#assign-an-editor-to-the-issue-to-manage-the-rest-of-the-review" title="Link to this heading">#</a></h3>
+<section id="assign-an-editor-to-the-issue-to-manage-the-rest-of-the-review-and-tag-the-issue-with-the-1-editor-assigned-tag-in-github">
+<h3>4. ✔️ Assign an editor to the issue to manage the rest of the review and tag the issue with the <code class="docutils literal notranslate"><span class="pre">1/editor-assigned</span></code> tag in GitHub<a class="headerlink" href="#assign-an-editor-to-the-issue-to-manage-the-rest-of-the-review-and-tag-the-issue-with-the-1-editor-assigned-tag-in-github" title="Link to this heading">#</a></h3>
 <p>Once the package initial checks are complete, and it is determined that
 the package is in scope for pyOpenSci review, the Editor in Chief will assign an
-editor to the review issue.
+editor to the review issue and add the <code class="docutils literal notranslate"><span class="pre">1/editor-assigned</span></code> tag in GitHub.
 This may involve finding a new (guest) editor
 as described in the <a class="reference internal" href="onboarding-guide.html"><span class="std std-doc">onboarding guide</span></a>.
 If you as Editor in Chief do recruit a new editor,
@@ -751,11 +751,11 @@ <h2>Responding to out-of-scope submissions<a class="headerlink" href="#respondin
 </ul>
 </li>
 <li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#editor-in-chief-checklist">Editor in Chief checklist</a><ul class="nav section-nav flex-column">
-<li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#tag-the-issue-with-1-editor-checks-tag-in-github">1. ✔️ Tag the issue with <code class="docutils literal notranslate"><span class="pre">1/editor-checks</span></code> tag in GitHub</a></li>
+<li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#tag-the-issue-with-0-pre-review-checks-tag-in-github">1. ✔️ Tag the issue with <code class="docutils literal notranslate"><span class="pre">0/pre-review-checks</span></code> tag in GitHub</a></li>
 <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#add-the-editor-checks-to-the-issue">2. ✔️ Add the editor checks to the issue</a></li>
 <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#editor-checklist-template">Editor-in-chief checklist</a></li>
 <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#ensure-that-the-package-onboarding-survey-is-filled-out">3. ✔️ Ensure that the package onboarding survey is filled out.</a></li>
-<li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#assign-an-editor-to-the-issue-to-manage-the-rest-of-the-review">4. ✔️ Assign an editor to the issue to manage the rest of the review</a></li>
+<li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#assign-an-editor-to-the-issue-to-manage-the-rest-of-the-review-and-tag-the-issue-with-the-1-editor-assigned-tag-in-github">4. ✔️ Assign an editor to the issue to manage the rest of the review and tag the issue with the <code class="docutils literal notranslate"><span class="pre">1/editor-assigned</span></code> tag in GitHub</a></li>
 <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#update-the-yaml-header-of-the-issue">5. ✔️ Update the YAML header of the issue</a></li>
 </ul>
 </li>