Pinning issues that require community feedback

[bytrangle]

I see that you have quite a number of issues that can only be moved forward with community feedback. How about selecting the most urgent, important ones and pinning them to get more attention? Currently, the pinned ones are collection of Pomodoro and tags, which I believe are only clicked by aspiring contributors.

[johannesjo]

This is a good idea, though it should always be very limited I think. Which ones would you like to see pinned?

[bytrangle]

Kanban board seems to be ever-popular, so probably some issues along that topic? I haven't read all the issues carefully, but I think the ability to duplicate a board is a given in any app that with Kanban feature, so it should be high priority I think.

[johannesjo]

Maybe we an alternative to pinning we could link to the community-feesback-wanted label in the readme?

[bytrangle]

I've jsut noticed that at least the first page of the Issues tab is mainly feature requests. This makes it hard to decide what to work on, and feature requests without context/explanation is pointless. It's my belief that feature requests are not issues.

What do you think about restricting feature requests to discussion tab only? To be specific, when one clicks the "New issue" button, show a dropdown list that includes "feature requests" which will direct to the Discussion tab?