It looks like the GUI improvement process will last for several weeks, so why don't we introduce a standardized workflow aimed at improving the communication channel between the community offering feedback and the devs turning this feedback into code?
We've already had 2 or 3 threads on this forum trying to tackle this communication loop but they've always ended up being quite chaotic as it's hard to keep track of so many issues at the same time if we just rely on a tool which is designed for facilitating discussion, not issue tracking.
Initially I was thinking about setting up a dedicated Excel spreadsheet but then I thought there is no need to reinvent the wheel as github offers very good tools for that. We just need to make a connection between github and this forum.
To make this practical, I would like to propose the following workflow:
(1) When you spot a non-critical bug or have some ideas for improvement, just make a post in this thread (ideally with screen-shots).
(2) If your idea is clearly non-controversial or you've received positive comments on the forum, open a new issue on github and paste a link to your forum post there.
(3) And to close the communication loop, paste the github link back to the forum post.If you don't have a github account (and you cannot be bothered to have one) just say so and someone else will do the github part for you.
This way an issue/improvement can be handled by the devs in a professional way on github and further clarifications can be offered there. Also, the feedback giver will be able monitor the progress (or lack of it) regarding the issue they've discovered or improvement they've proposed. At the same time, since we have the issue/improvement posted on the forum, the community will be able to offer comments and thoughts about it and help to estimate how important it is (or maybe it does not make sense at all).
What do you think?
Topic: Standardized workflow for issues/improvements in the GUI (Read 13985 times)
