Replace support question template with contact links#4
Conversation
|
My opinion still stands on this topic: reducing the reference to the chat because important questions and answers are lost after few hours and days in a chat group.
More informations and background like this can be found in a related pull request on the old maintainer repository: zendframework/maintainers#60 I myself will not answer any support questions in the chat because I'm not wasting my time writing in a black hole. |
|
I agree with @froschdesign that losing chat history is a big problem. Even if we keep the history it will be very hard to search for questions/answers there. Not sure how it is solved by others (doctrine?) |
As said in the past, I do not want to hide or kill the chat because this has its advantages and justification. But for support questions it is a dead end when the history is regularly lost. So pushing the user to the chat is the wrong direction. (imo) |
|
Reading your replies I guess the best option is to merge the two and create a "feedback/support" selection which redirects to discourse? |
|
Actually it makes sense. If people are ready to create new issue they can as well create new forum post. There are other ways to discover chat. |
|
Options are updated to lead to forums, support questions leads directly to questions category |
| blank_issues_enabled: false | ||
| contact_links: | ||
| - name: ❓ Support Question | ||
| url: https://discourse.laminas.dev/c/questions/5 |
There was a problem hiding this comment.
Maybe we should have here link:
https://discourse.laminas.dev/c/questions/expressive/7
And for laminas we have:
https://discourse.laminas.dev/c/questions/components/6
There was a problem hiding this comment.
Good point.
This brings a new task: update the forum. (I will ask @weierophinney if I can do that.)
There was a problem hiding this comment.
I agree. But at this time I'm not sure those categories will remain. They might be just renamed or might be archived.
There was a problem hiding this comment.
I hope we can rename them and old links will be redirected, but not sure if it is possible?
There was a problem hiding this comment.
@michalbundyra Category text name does not matter, it is just for link readability. It is routed by id.
There was a problem hiding this comment.
There was a problem hiding this comment.
I agree that we should link to the specific category for the given project/subproject. @froschdesign has already renamed them (as he's noted in the comment prior to mine). I think with that change, we can get these merged against all three orgs.
I like the way from Hugo. The Gitter chat contains this note at the top of the page:
And on the website they have 3 links:
|
Xerkus
force-pushed
the
feature/support-add-button
branch
from
c8e47ec to
0476494
Compare
5 participants
Support question issue template confuses users.
This pull request replaces template with contact links that will be displayed as a button leading to chat or forums instead of creating new issue.
Mirrors laminas/.github#5