deploy: a3499b6

how_to/nominate.html

@@ -185,6 +185,7 @@ <h2 id="how-to-nominate"><a class="header" href="#how-to-nominate">How to nomina
 Where should we go from here?
 </code></pre>
 <p>The ideal comment will identify precisely what question you would like answered. Please try to make the comment easy for us to parse and understand without requiring a lot of context. We encourage links to internals or Zulip so we can dive into the details, but it really helps us give useful answers if you can summarize the key details up front.</p>
+<p>If you're not a member of the Rust team on GitHub you'll get an error from rustbot when trying to add the label - please make the comment (following the guidelines above) anyway, and ping the lang team on our (chat platform)[../chat_platform.md) asking for the label to be added.</p>
 <p>If your comment requires more than 5-10 minutes of reading and discussion to understand and effectively respond to, consider <a href="./design_meeting.html">filing a meeting proposal</a> instead. This will give you ~60 minutes to present your question and the lang team more time to analyze it. We may punt the question back to you with an ask to do so if the question isn't answerable in our triage meeting time.</p>
 <h2 id="how-quickly-will-the-lang-team-answer"><a class="header" href="#how-quickly-will-the-lang-team-answer">How quickly will the lang team answer?</a></h2>
 <p>We try to be prompt, but sometimes we are not. Othertimes, we discuss the issue, but fail to leave the follow-up comment, because we're only human. Please feel free to raise the topic on Zulip or reach out to a lang team member.</p>

how_to/propose.html

@@ -275,7 +275,7 @@ <h3 id="what-about-adding-special-traits-and-things-to-the-standard-library"><a
 <p>We consider intrinsics and &quot;lang item&quot; (things that need special treatment from the language) to be under the lang team purview. Specifically, the lang team governs the semantics and capabilities exposed by this new feature. The details of the API are governed by the <a href="https://github.com/rust-lang/libs-team">libs-api team</a>.</p>
 <p>Whenever possible, though, we prefer to issue a quick approval for the &quot;general feature&quot; being discussed, and leave it to the libs-api team to decide where to apply it. For example, we approved the ability to add inherent methods to standard library types like <code>u32</code> long ago, but the <a href="https://github.com/rust-lang/libs-team">libs-api team</a> governs what APIs are available.</p>
 <h3 id="my-rfc-has-been-waiting-for-a-comment-from-the-lang-team-for-a-long-time"><a class="header" href="#my-rfc-has-been-waiting-for-a-comment-from-the-lang-team-for-a-long-time">My RFC has been waiting for a comment from the lang-team for a long time!</a></h3>
-<p>First off, I'm sorry, that sucks. We are aware that we need to do a better job keeping up with RFCs. :/ That said, what you can do is to <a href="./nominate.html">nominate</a> the RFC and we will discuss it during the meeting.</p>
+<p>First off, I'm sorry, that sucks. We are aware that we need to do a better job keeping up with RFCs :/ (as long as it's tagged with <code>T-lang</code>, we'll know it exists). That said, what you can do is to <a href="./nominate.html">nominate</a> the RFC and we will discuss it during the meeting.</p>
 
  </main>
 

print.html

@@ -213,6 +213,7 @@ <h2 id="how-to-nominate"><a class="header" href="#how-to-nominate">How to nomina
 Where should we go from here?
 </code></pre>
 <p>The ideal comment will identify precisely what question you would like answered. Please try to make the comment easy for us to parse and understand without requiring a lot of context. We encourage links to internals or Zulip so we can dive into the details, but it really helps us give useful answers if you can summarize the key details up front.</p>
+<p>If you're not a member of the Rust team on GitHub you'll get an error from rustbot when trying to add the label - please make the comment (following the guidelines above) anyway, and ping the lang team on our (chat platform)[../chat_platform.md) asking for the label to be added.</p>
 <p>If your comment requires more than 5-10 minutes of reading and discussion to understand and effectively respond to, consider <a href="how_to/./design_meeting.html">filing a meeting proposal</a> instead. This will give you ~60 minutes to present your question and the lang team more time to analyze it. We may punt the question back to you with an ask to do so if the question isn't answerable in our triage meeting time.</p>
 <h2 id="how-quickly-will-the-lang-team-answer"><a class="header" href="#how-quickly-will-the-lang-team-answer">How quickly will the lang team answer?</a></h2>
 <p>We try to be prompt, but sometimes we are not. Othertimes, we discuss the issue, but fail to leave the follow-up comment, because we're only human. Please feel free to raise the topic on Zulip or reach out to a lang team member.</p>
@@ -339,7 +340,7 @@ <h3 id="what-about-adding-special-traits-and-things-to-the-standard-library"><a
 <p>We consider intrinsics and &quot;lang item&quot; (things that need special treatment from the language) to be under the lang team purview. Specifically, the lang team governs the semantics and capabilities exposed by this new feature. The details of the API are governed by the <a href="https://github.com/rust-lang/libs-team">libs-api team</a>.</p>
 <p>Whenever possible, though, we prefer to issue a quick approval for the &quot;general feature&quot; being discussed, and leave it to the libs-api team to decide where to apply it. For example, we approved the ability to add inherent methods to standard library types like <code>u32</code> long ago, but the <a href="https://github.com/rust-lang/libs-team">libs-api team</a> governs what APIs are available.</p>
 <h3 id="my-rfc-has-been-waiting-for-a-comment-from-the-lang-team-for-a-long-time"><a class="header" href="#my-rfc-has-been-waiting-for-a-comment-from-the-lang-team-for-a-long-time">My RFC has been waiting for a comment from the lang-team for a long time!</a></h3>
-<p>First off, I'm sorry, that sucks. We are aware that we need to do a better job keeping up with RFCs. :/ That said, what you can do is to <a href="how_to/./nominate.html">nominate</a> the RFC and we will discuss it during the meeting.</p>
+<p>First off, I'm sorry, that sucks. We are aware that we need to do a better job keeping up with RFCs :/ (as long as it's tagged with <code>T-lang</code>, we'll know it exists). That said, what you can do is to <a href="how_to/./nominate.html">nominate</a> the RFC and we will discuss it during the meeting.</p>
 <div style="break-before: page; page-break-before: always;"></div><h1 id="how-do-i-propose-a-new-lint-or-extend-an-existing-one"><a class="header" href="#how-do-i-propose-a-new-lint-or-extend-an-existing-one">How do I propose a new lint, or extend an existing one?</a></h1>
 <p>For small lints, you can follow the <a href="how_to/./propose.html">policy for smaller changes</a>: implement the lint, open a PR, and then <a href="how_to/./nominate.html">nominate</a> it for lang-team attention. </p>
 <p>We may request an RFC if:</p>