[Communication]: Create is-this-known channel
Problem
There has been some previous discussion here and there about this:
To me it seems like we have started using several channels (e.g. #frontend, #questions and #development) to ask “Is this known”? This is not that nice, because it is not “Issue First”, noisy and often questions are duplicated across those channels. Sometimes those questions are also are asking if intended changes were really intended or are regressions, we are moving so fast it is hard to keep up with all UI changes.
I'll expand on some points:
Issue First
We effectively state in the handbook that everything should start with an issue, but often the interaction in a "Is this known" goes like this: Question is asked, answer is "no". No issue has been created.
Noisy
Often people enter and leave the #frontend channel just to ask a "is this known", this reduces the usefulness of the frontend channel, because Frontend topics get lost in between the left/join system messages and the "is-this-known" question.
Duplicated questions
The questions can be duplicated across channels, and this ultimately might lead to mis-information.
Examples:
This issue has been: https://gitlab.com/gitlab-org/gitlab-ce/issues/55282 "is-this-knowned" several times:
- https://gitlab.slack.com/archives/C02PF508L/p1544676733401800
- https://gitlab.slack.com/archives/C0GQHHPGW/p1544677666207700
- https://gitlab.slack.com/archives/C0GQHHPGW/p1544782582246300
- https://gitlab.slack.com/archives/C8S0HHM44/p1544662484302600
Sometimes we have "is-this-knowns" that are not regressions, but actually wanted changes like this one: https://gitlab.slack.com/archives/C0AR2KW4B/p1544737179395400
Solution
Introducing a channel #is-this-known
to have a central point to ask those gitlab.com/product "is-this-known" related questions.