Updating references to meteor-feature-requests repository

.github/ISSUE_TEMPLATE.md

@@ -2,7 +2,7 @@
 * ❓ Questions?
           Start a discussion on the Meteor forums (https://forums.meteor.com/) or post a message on (Community Slack)[https://join.slack.com/t/meteor-community/shared_invite/enQtODA0NTU2Nzk5MTA3LWY5NGMxMWRjZDgzYWMyMTEyYTQ3MTcwZmU2YjM5MTY3MjJkZjQ0NWRjOGZlYmIxZjFlYTA5Mjg4OTk3ODRiOTc]
 * 💡 Feature requests?
-          Visit the feature request repository (https://github.com/meteor/meteor-feature-requests).
+          Visit our Discussions page (https://github.com/meteor/meteor/discussions).
 * ❗️ Bug?
           This is the right place!
 
@@ -25,7 +25,7 @@ If you don't include a reproduction the issue is probably going to be closed.
 
 Please ensure your issue is opened in the appropriate repository:
 
-* Feature Requests: https://github.com/meteor/meteor-feature-requests
+* Feature Requests: https://github.com/meteor/meteor/discussions
 * Blaze: https://github.com/meteor/blaze/
 * Docs: https://github.com/meteor/docs/
 * Guide: https://github.com/meteor/guide/

.github/PULL_REQUEST_TEMPLATE.md

@@ -9,7 +9,7 @@ Here are some important details to follow:
           This is especially true for feature requests!
 * 💡 Features
           Feature requests can be created and discussed by visiting:
-          https://github.com/meteor/meteor-feature-requests/issues
+          https://github.com/meteor/meteor/discussions
 * 🕷 Bug fixes
           These can be created and discussed in this repository. When fixing a bug,
           please _try_ to add a test which verifies the fix.  If you cannot, you should

CONTRIBUTING.md

@@ -140,7 +140,7 @@ for more details on proposing changes to core code.
 
 ## Feature requests
 
-Feature requests are tracked in the [meteor/meteor-feature-requests](https://github.com/meteor/meteor-feature-requests) repository, and include a label that corresponds to the Meteor subproject that they are a part of.
+Feature requests are tracked in the [Discussions](https://github.com/meteor/meteor/discussions).
 
 Meteor is a big project with [many sub-projects](https://github.com/meteor/meteor/tree/devel/packages).
 Community is welcome to help in all the sub-projects. We use our [roadmap](Roadmap.md) to communicate the high-level features we're currently prioritizing.
@@ -216,7 +216,7 @@ For more information about how to work with Meteor core, take a look at the [Dev
 
 ### Proposing your change
 
-You'll have the best chance of getting a change into core if you can build consensus in the community for it or if it is listed in the [roadmap](https://github.com/meteor/meteor/blob/devel/Roadmap.md). Start by creating a well specified feature request as a Github issue, in the [meteor/meteor-feature-requests](https://github.com/meteor/meteor-feature-requests) repository.
+You'll have the best chance of getting a change into core if you can build consensus in the community for it or if it is listed in the [roadmap](https://github.com/meteor/meteor/blob/devel/Roadmap.md). Start by creating a well specified Discussion [here](https://github.com/meteor/meteor/discussions).
 
 Help drive discussion and advocate for your feature on the Github ticket (and perhaps the forums). The higher the demand for the feature and the greater the clarity of it's specification will determine the likelihood of a core contributor prioritizing your feature by flagging it with the `ready` label.
 

ISSUE_TRIAGE.md

@@ -1,6 +1,6 @@
 # Issue Triage
 
-This document describes the process Meteor contributors use to organize issues. We use Github [issues](https://github.com/meteor/meteor/issues) in this repository to track bugs, and [meteor/meteor-feature-requests](https://github.com/meteor/meteor-feature-requests) to track feature requests. Our goal is to maintain a list of issues that are relevant and well-defined (and [labeled](https://github.com/meteor/meteor/labels)) such that a contributor can immediately begin working on the code for a fix or feature request. Contributors who want to dive in and write code aren't likely to prioritize working on issues that are ambiguous and have low impact.
+This document describes the process Meteor contributors use to organize issues. We use Github [issues](https://github.com/meteor/meteor/issues) in this repository to track bugs, and [Discussions](https://github.com/meteor/meteor/discussions) to track feature requests. Our goal is to maintain a list of issues that are relevant and well-defined (and [labeled](https://github.com/meteor/meteor/labels)) such that a contributor can immediately begin working on the code for a fix or feature request. Contributors who want to dive in and write code aren't likely to prioritize working on issues that are ambiguous and have low impact.
 
 You can filter issues that are missing triage using this [filter](https://github.com/meteor/meteor/issues?q=is%3Aissue+is%3Aopen+-label%3Aconfirmed+-label%3Anot-ready+-label%3Ain-discussion+-label%3Aneeds-reproduction+-label%3Aready+-label%3Ain-development++-label%3Apending-tests+-label%3Awaiting-feedback): `is:issue is:open -label:confirmed -label:not-ready -label:in-discussion -label:needs-reproduction -label:ready -label:in-development -label:pending-tests -label:waiting-feedback`
 

README.md

@@ -66,7 +66,7 @@ Interested in helping or contributing to Meteor?  These resources will help:
 
 * [Core development guide](DEVELOPMENT.md)
 * [Contribution guidelines](CONTRIBUTING.md)
-* [Feature requests](https://github.com/meteor/meteor-feature-requests/)
+* [Feature requests](https://github.com/meteor/meteor/discussions/)
 * [Issue tracker](https://github.com/meteor/meteor/issues)
 
 ## Uninstalling Meteor

Roadmap.md

@@ -36,17 +36,9 @@ Updated at: 2021/01/20
 
 Meteor is accelerating! We are going release more often this year.
 
-We expect to have new features focusing in ease app development in V3 or probably in V2 as well, the first step is to review our [feature requests](https://github.com/meteor/meteor-feature-requests) one more time and define new priorities.
+We expect to have new features focusing in ease app development in V3 or probably in V2 as well.
 
-Maybe we should also have a new way of prioritization for new features, right now this [repository]((https://github.com/meteor/meteor-feature-requests)) with issues is not good enough in our opinion, the plan is to be even more open for feedbacks and collaboration. If we make changes in this process we are going to announce in the [Forums](https://forums.meteor.com/) and Slack as always.
-
-> We are also looking for new developers to be part of our core team and of course if you are already contributing to Meteor you have a head start.
-> 
-> We don't have an official position description yet but again, contributing to Meteor in the open-source is the best way to join the core team.
-
-Maybe you are asking: Why the format of this Roadmap was changed in this update?
-
-We believe the items here were in some part outdated so we want to have a "fresh start". You should expect a new list of items here soon. It doesn't mean that all the old items are out of question, or they aren't important, probably the opposite and you will see most of them again here soon.
+See feature requests and other discussions [here](https://github.com/meteor/meteor/discussions)
 
 ## Recently completed