Commit 005ce32f authored by Job van der Voort's avatar Job van der Voort

Merge branch 'cleanup-feature-proposal' into 'master'

Cleanup feature proposal template

## What does this MR do?

Changes the recommended template for feature proposals.

## Are there points in the code the reviewer needs to double check?

## Why was this MR needed?

I've been using the template for a while, and find that putting so many words into the h2 makes me think there's actual content there, until I realize I'm just reading the template text (again). I think we can get away with just putting `Description` as the header, and putting the suggested content for that section as plain text below for someone to replace.

## What are the relevant issue numbers?

## Screenshots (if relevant)

![image](/uploads/20a99c98a12aad84c1a7ec020f365b2f/image.png)

/cc @JobV 

See merge request !5240
parents f17a753d 81a34f2f
......@@ -145,7 +145,8 @@ might be edited to make them small and simple.
You are encouraged to use the template below for feature proposals.
```
## Description including problem, use cases, benefits, and/or goals
## Description
Include problem, use cases, benefits, and/or goals
## Proposal
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment