meta: broaden stale bot · nodejs/node@5e14e4d

along with other issues and may or may not decide to

work on an implementation or advocate on their behalf.

If a collaborator believes a feature request must be implemented

they can add the `never-stale` label to the issue and it will

be excluded from the automated feature request handling

as outlined below.

## Expressing support for a feature request

If you come across a feature request and want to add your

support for that feature please express your support

with the thumbs up emoji as a reaction. At some point in the

future we may use this as additional input in the automated

handling of feature requests.

## Automated feature request handling

Our experience is that most feature requests that are

likely to be addressed, will be addressed within the first

6 months after they are submitted.

Once there has been no activity on a feature request for

5 months, the following comment will be added

to the issue:

```markdown

There has been no activity on this feature request for

5 months and it is unlikely to be implemented.

It will be closed 6 months after the last non-automated comment.

For more information on how the project manages

feature requests, please consult the

[feature request management document](https://github.com/nodejs/node/blob/HEAD/doc/contributing/feature-request-management.md).

```

If there is no additional activity/discussion on the

feature request in the next month, the following

comment is added to the issue and the issue will be

closed:

```markdown

There has been no activity on this feature request

and it is being closed. If you feel closing this issue is not the

right thing to do, please leave a comment.

For more information on how the project manages

feature requests, please consult the

[feature request management document](https://github.com/nodejs/node/blob/HEAD/doc/contributing/feature-request-management.md).

```