From d4dd1f059236e1bc3a38d665b67715ede2955362 Mon Sep 17 00:00:00 2001 From: Manish Goregaokar Date: Wed, 17 Jan 2018 22:58:15 +0530 Subject: [PATCH] Issues are not feature requests --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 9a0b58567..162eb246d 100644 --- a/README.md +++ b/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. You may file issues +on this repo for discussion, but these are not actively looked at by the teams. As a rule of thumb, receiving encouraging feedback from long-standing project developers, and particularly members of the relevant [sub-team] is a good