e1438cc83a
We had this problem in Mattermost where when we used the term "Feature Requests" it sounded a bit like "Pull Requests" and there was an expectation sometimes, in our own team and in the community, that it was some sort of formal ticket that had to be addressed. We later changed to "Feature Idea" and then the expectations changed, where the maintainers didn't necessarily need to address every new ticket, since it was more sharing an idea, versus putting in a request. Right now the volume of feature ideas is a little overwhelming and my sense is we should make this change to lower the perceived pressure a bit. If we make this change, we can go update the previous tickets to match, and link to this ticket to explain why.
367 B
367 B
| name | about | title | labels | assignees |
|---|---|---|---|---|
| Enhancement / Feature Idea | Suggest a new capability | Feature Idea: | enhancement |
Summary: What the new capability is.
How important this is to me and why:
Importance: High/Medium/Low
Use cases: 1. 2. 3.
Additional context / similar features: Any examples of good implementations of this capability.