GeezerVison is showing github.com — doc: clarify status of feature request issues · nodejs/node@5a9874a
File tree
Expand file treeCollapse file tree
Open diff view settings
Expand file treeCollapse file tree
Open diff view settings
Collapse file
Copy file name to clipboardExpand all lines: doc/contributing/feature-request-management.md +10-8Lines changed: 10 additions & 8 deletions - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
|
1 | 1 | # Feature request management |
2 | 2 |
|
3 | | -Feature requests are a valuable source of input to the project. |
4 | | -They help our maintainers understand what additions will be of |
5 | | -value to users of the Node.js runtime. |
6 | | - |
7 | | -At the same time, the project is volunteer run and does not |
8 | | -have the ability to direct resources toward specific work. The |
9 | | -features which are implemented are those for which volunteers |
10 | | -are individually motivated to work on. The best way to ensure |
| 3 | +Feature requests are not a valuable source of input for the project. |
| 4 | +It is usually more productive to first send the Pull Request implementing the |
| 5 | +feature, even imperfectly, and let the discussion happen during code review. |
| 6 | +That being said, the project still welcomes feature request issues, either for |
| 7 | +features you cannot and/or won't implement yourself, or if you need more input |
| 8 | +from the community before starting the work. |
| 9 | + |
| 10 | +The project is volunteer run and does not have the ability to direct resources |
| 11 | +toward specific work. The features which are implemented are those for which |
| 12 | +volunteers are individually motivated to work on. The best way to ensure |
11 | 13 | a feature gets implemented is to create a PR to add it. |
12 | 14 | The project strives to support people who do that. |
13 | 15 |
|
|