Merge pull request #252 from aidanhs/aphs-rfc-clarifications

Notes from my RFC experience

src/how_to/nominate.md

@@ -19,6 +19,8 @@ Where should we go from here?
 
 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.
 
+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.
+
 If your comment requires more than 5-10 minutes of reading and discussion to understand and effectively respond to, consider [filing a meeting proposal](./design_meeting.md) 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.
 
 ## How quickly will the lang team answer?

src/how_to/propose.md

@@ -133,4 +133,4 @@ Whenever possible, though, we prefer to issue a quick approval for the "general
 
 ### My RFC has been waiting for a comment from the lang-team for a long time!
 
-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 [nominate](./nominate.md) the RFC and we will discuss it during the meeting.
+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 `T-lang`, we'll know it exists). That said, what you can do is to [nominate](./nominate.md) the RFC and we will discuss it during the meeting.