├── .github └── ISSUE_TEMPLATE.md ├── LICENSE └── README.md /.github/ISSUE_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | ### Before opening a new feature request, please note: 2 | 3 | - Issues in this repository are reserved for feature requests only. Bugs should be reported in the main [Meteor repo issue tracker](https://github.com/meteor/meteor). 4 | - Check to see if a similar feature request already exists or has been closed before. 5 | 6 | ### Feature requests should include as much detail as possible: 7 | - [ ] A descriptive title 8 | - [ ] A description of the problem you're trying to solve, including *why* you think this is a problem 9 | - [ ] An overview of the suggested solution 10 | - [ ] If the feature changes current behavior, reasons why your solution is better 11 | 12 | See [here](https://github.com/meteor/meteor/blob/devel/CONTRIBUTING.md#feature-requests) for more detail on what is expected of a feature request. 13 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | The MIT License (MIT) 2 | 3 | Copyright (c) 2011 - 2017 Meteor Development Group, Inc. 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | 23 | 24 | ==================================================================== 25 | This license applies to all code in Meteor that is not an externally 26 | maintained library. Externally maintained libraries have their own 27 | licenses, included in the LICENSES directory. 28 | ==================================================================== 29 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Meteor Feature Requests (DEPRECATED) 2 | 3 | This repository is no longer used and it is now in read-only mode. We are using GitHub Discussions in our main repository as a replacement of this repository. 4 | 5 | Read more [here](https://github.com/meteor/meteor/discussions/11504) 6 | 7 | ## OLD README 8 | 9 | This repository is used to track [Meteor](https://github.com/meteor/meteor) feature requests only (requests for new Meteor functionality). Click [here](https://github.com/meteor/meteor-feature-requests/issues/new) to open a new feature request. 10 | 11 | **Note:** Meteor bugs are tracked in the [Meteor repo issue tracker](https://github.com/meteor/meteor/issues). 12 | 13 | ## Guidelines 14 | 15 | We use our [roadmap](https://github.com/meteor/meteor/blob/devel/Roadmap.md) to communicate the high-level features we're currently prioritizing. 16 | 17 | Every additional feature adds a maintenance cost in addition to its value. This cost starts with the work of writing the feature or reviewing a community pull request. In addition to the core code change, attention needs to be paid to documentation, tests, maintainability, how the feature interacts with existing and speculative Meteor features, cross-browser/platform support, user experience/API considerations, etc. Once the feature is shipped, it then becomes the community's responsibility to fix future bugs related to the feature. In case the original author disappears, it's important that the feature has good tests and is widely used in order to be maintainable by other contributors. 18 | 19 | For these reasons, we strongly encourage features to be implemented as npm or Atmosphere packages rather than changes to core. Try to re-work your feature request as a minimal set of hooks to core that enable the feature to be implemented as a package. 20 | 21 | Feature requests should be well specified and unambiguous to have the greatest chance of being worked on by a contributor. 22 | 23 | Finally, you can show your support for (or against!) features by using GitHub reactions or by adding meaningful details which help the feature definition become more clear. Please do not comment with "+1" since it creates a lot of noise (e-mails, notifications, etc.). 24 | 25 | ## Resources 26 | 27 | - Main Meteor repo: https://github.com/meteor/meteor 28 | - Contribution guidelines: https://github.com/meteor/meteor/blob/devel/CONTRIBUTING.md 29 | - Feature request triaging guidelines: https://github.com/meteor/meteor/blob/devel/ISSUE_TRIAGE.md#feature-requests 30 | - Feature request (PR) development guide: https://github.com/meteor/meteor/blob/devel/DEVELOPMENT.md 31 | --------------------------------------------------------------------------------