Issues are not feature requests

README.md

@@ -85,9 +85,9 @@ beforehand, to ascertain that the RFC may be desirable; having a consistent
 impact on the project requires concerted effort toward consensus-building.
 
 The most common preparations for writing and submitting an RFC include talking
-the idea over on #rust-internals, filing and discussing ideas on the
-[RFC issue tracker], and occasionally posting "pre-RFCs" on the
-[developer discussion forum] for early review.
+the idea over on #rust-internals, discussing the topic on our [developer discussion forum],
+and occasionally posting "pre-RFCs" on the developer forum. Please do not file
+feature requests as issues on this repo.
 
 As a rule of thumb, receiving encouraging feedback from long-standing project
 developers, and particularly members of the relevant [sub-team] is a good
@@ -251,6 +251,22 @@ consensus and community norms, not impose more structure than necessary.
 [RFC repository]: http://github.com/rust-lang/rfcs
 [sub-team]: http://www.rust-lang.org/team.html
 
+## Issues on this repo
+
+As mentioned before, the issues on this repo are not for feature requests.
+
+They may be used for:
+
+ - Cleanup/housekeeping of the repo itself
+ - Tracking multi-rfc endeavors
+ - Recording general problem statements the Rust teams wish to eventually solve
+
+For the last one this is basically for listing problems for which there
+is general consensus that we _want_ to solve the problem, but have not
+yet settled on a solution. Such issues can be used for tracking any
+discussions that occur on the internals forum relevant to this topic,
+as well as tracking any RFCs which potentially may solve the problem.
+
 ## License
 [License]: #license