[nautilus/antoniof-master-patch-72558: 554/555] issue_templates: Redirect feature requests

[António Fernandes <antoniof src gnome org>]

commit 1fda89f1732c7739fbf1a9bb5cf91e1c0d4776ec
Author: António Fernandes <antoniojpfernandes gmail com>
Date:   Fri Jul 23 20:22:01 2021 +0000

    issue_templates: Redirect feature requests
    
    The existing Feature issue template is tailored for contributors who
    understand the process, have insight on benefits and drawbacks.
    
    In practice, that's a minority of the people how use the template.
    For everybody else, the template appears to encourage submission of
    features requests without previous community discussion. This often
    results in poor quality issue descriptions which lack actual use
    cases and naïvely assert there are no drawbacks. Poor quality issues
    end up being closed, which sends negative vibes, feeding frustration
    and unproductive behaviors.
    
    Aiming to avoid the negativity trap and promote community engagement,
    point people in the direction of Discourse and the place to discuss
    ideas. Also, repurpose the template to get more useful information on
    the underlying problems motivating an enhancement or feature request.

 .gitlab/issue_templates/Feature.md | 33 +++++++++++++++++++--------------
 1 file changed, 19 insertions(+), 14 deletions(-)
---
diff --git a/.gitlab/issue_templates/Feature.md b/.gitlab/issue_templates/Feature.md
index 426acf965..9a2b4c43b 100644
--- a/.gitlab/issue_templates/Feature.md
+++ b/.gitlab/issue_templates/Feature.md
@@ -1,22 +1,27 @@
+<!--
+     Do you have a feature request?
+     Ideas for new features are welcome and there is a nicer place for them:
+     
+     https://discourse.gnome.org/tag/nautilus
+
+     Add your feature suggestion as a new topic in the above website.
+-->
+<!--
+     While you are here, please report how the existing features have failed
+     to meet your needs or made it too difficult to perform some tasks.
+-->
 ### Use cases
-<!-- Describe what problem(s) the user is experiencing and that this request
-is trying to solve. -->
+<!-- Describe your needs and constraints. Examples from real world situations are useful. -->
 
 
-### Desired behavior
-<!-- Describe the desired functionality. -->
+### Available features and workarounds
+<!-- How do you manage with the current version of the application? -->
 
 
-### Benefits of the solution
-<!-- List the possible benefits of the solution and how it fits in the project. -->
+### Difficulties or shortcomings
+<!-- Why is the current experience unsatisfying? -->
 
 
-### Possible drawbacks
-<!--
-     Describe possible drawbacks of the feature and list how it could affect
-     the project i.e. UI discoverability, complexity, impact in more or less
-     number of users, etc.
--->
+### Possible enhancements
+<!-- What could improve the situation? -->
 
-<!-- Ignore the text under this line. -->
-/label ~"1. Feature"