Skip to content

Commit d4dd1f0

Browse files
committed
Issues are not feature requests
1 parent c892139 commit d4dd1f0

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -85,9 +85,9 @@ beforehand, to ascertain that the RFC may be desirable; having a consistent
8585
impact on the project requires concerted effort toward consensus-building.
8686

8787
The most common preparations for writing and submitting an RFC include talking
88-
the idea over on #rust-internals, filing and discussing ideas on the
89-
[RFC issue tracker], and occasionally posting "pre-RFCs" on the
90-
[developer discussion forum] for early review.
88+
the idea over on #rust-internals, discussing the topic on our [developer discussion forum],
89+
and occasionally posting "pre-RFCs" on the developer forum. You may file issues
90+
on this repo for discussion, but these are not actively looked at by the teams.
9191

9292
As a rule of thumb, receiving encouraging feedback from long-standing project
9393
developers, and particularly members of the relevant [sub-team] is a good

0 commit comments

Comments
 (0)