Streamline reactions: nofr+close

[TwizzyDizzy]

Usage: @rocket-cat nofr+close [REPORTER USERNAME]

Here is my suggestion for a bot template to close an issue, label it as "unrefined-feature-request" and give a feedback to the user.

This is for closing issues that are feature requests that have not been discussed by the community and have not been refined to an extent that allows immediate implementation.

There might be feature requests though, that are extremely concise and allow immediate implementation because of their limited scope and clear definition. Those feature requests are not meant with this reaction.

This reaction describes procedures that are not in place to date and need to be implemented before that.

Cheers
Thomas

Hi [REPORTER USERNAME]

First off: thank you for taking interest in Rocket.Chat and its improvement. Unfortunately though, I am closing this issue because this is a feature request. The usual procedure for feature requests is as follows:

• feature request is incoming via the feature requests category in the forums
• feature request is pre-approved by Rocket.Chat team member
• feature request is discussed and refined until it is utterly clear what is to be implemented and what is to be achieved by the feature request. Technical details might be part of this discussion
• feature is approved by Rocket.Chat team member (or not - then it will not be done by the Rocket.Chat team - yet might still be done as a Rocket.Chat App by the community)
• feature request is transferred to github and labelled with "Feature: Planned"

Please understand, that we do not want to clutter Github with wishes and ideas as we have decided to use the forums for that.

When you compose a feature request in the forums, please ask yourself the following questions:

• is my feature request something that benefits everybody or at least a great amount of people
• is my feature request something that is technically possible (only if you have the expertise)
• [... maybe more?...]

[GENERIC ROCKET.CHAT SALUTATION]
[USERNAME OF THE ONE WHO TRIGGERED THE BOT]