19

In the PHP collective, we are seeing a lot of discussion posts that should have been questions. These posts generally include a lot of code, which is a flag (in my mind) that they should have been a question, as I would expect discussion topics to have minimal code in them (if we're discussing code, we should probably be on Code Review).

Could the question wizard for discussions be modified to enforce a higher words to code ratio? I think that would largely resolve this issue.

Alternatively - and maybe this is a better solution - could we have a way for recognised members to automatically migrate a discussion post to a question instead?

Or can we have proper moderation tools - e.g. close and delete voting, expanded flagging - for recognised members of the collective?

Any suggestions as to whether there might be an even better way?

13
  • 13
    Are you really sure you want those posts to become questions? What fraction of them would likely be duplicates? How often do they already meet focus/clarity etc. standards? Commented Nov 30, 2023 at 10:32
  • 3
    I don't think that increasing the text-to-code ratio is a good idea. I'm already using my "Please do not post garbage or duplicated content to get around the quality filter" quite a lot. If the threshold is increased, people will just pour more garbage in to get around that "stupid filter", because their question is perfect as it is and no mean computer shall deter them from posting.
    – Adriaan
    Commented Nov 30, 2023 at 10:52
  • 4
    @KarlKnechtel at least as questions we can quickly close/delete if required. As discussions, we have to wait for a CM to get around to getting rid of them. But yeah, perhaps the better way is to allow discussions to be close and delete voted.
    – Nick
    Commented Nov 30, 2023 at 11:23
  • 1
    @Adriaan I know, the garbage issue happens a lot and this might make it worse. If we could instead migrate to questions, they could quickly be closed and deleted if required.
    – Nick
    Commented Nov 30, 2023 at 11:24
  • 7
    This is kind of similar to migrating to different sites, IMO. That kind of stopped being done because the recipient site was generally not too happy with the content being dumped into their lap. Let's learn from that and not migrate discussions to questions. Chances are, we don't want 'em.
    – Gimby
    Commented Nov 30, 2023 at 12:44
  • 1
    I would hate to move discussions to questions as we are not being able to close all questions that needs to be closed. Adding more to that is not something I would welcome. If the discussion is supposed to be the question, it should just be removed.
    – Dalija Prasnikar Mod
    Commented Nov 30, 2023 at 13:52
  • I mean, making it impossible to find seems to have been somewhat effective for chat,
    – Kevin B
    Commented Nov 30, 2023 at 14:13
  • @DalijaPrasnikar I think the point is that, with questions, we at least have the tools to deal with crap; Discussions don't have any of that tooling at the moment, which makes these cases harder to deal with.
    – zcoop98
    Commented Nov 30, 2023 at 16:44
  • 4
    @zcoop98 Yes, I understand that. But IMO the solution to moderating discussions has to be a proper solution for discussions, not dumping what does not belong there back to Q/A. From what I have seen plenty of those question in discussions are literally a duplicate of questions those user already posted in Q/A. It makes zero sense to add those as duplicates. It would also just incentivize people to go to discussions first for posting questions.
    – Dalija Prasnikar Mod
    Commented Nov 30, 2023 at 16:51
  • I'd love to see some suggestions as answers. It would seem so far that proper moderation tools for recognised members is the way to go so we can just deal with this problem at its source.
    – Nick
    Commented Nov 30, 2023 at 23:18
  • We also have to keep in mind that discussions are new. We have to allow the possibility for them to be recognised as another failed experiment, if people don't use them responsibly. Whatever happens with it, let "them" handle it. At this point we'd not be fixing a problem, but sweeping information under the rug.
    – Gimby
    Commented Dec 1, 2023 at 7:57
  • 1
    Note that there will be a flag reason for it: "Should be a question". Though this doesn't satisfactorily address the question of scaling for me. I agree that some kind of interface guidance for the discussion initiator would be useful.
    – starball
    Commented Dec 1, 2023 at 21:08
  • 1
    @starball can't wait for that feature to actually be implemented...
    – Nick
    Commented Dec 2, 2023 at 0:31

1 Answer 1

7

Asking programming-specific questions which belong on Stack Overflow Q&A is only discouraged, not prohibited in Discussions. As such, the correct response is to jump into the discussion yourself and suggest that perhaps the question would be better asked in the normal Stack Overflow Q&A.

I guess it makes sense, if you're after a back-and-forth about your question. That kind of discussion doesn't follow the Q&A format.

Whether the existence of Discussions detracts from the existing Q&A format... That's a different question.

2
  • 4
    I've got to the point of having a canned "This should be a question, not a discussion post." comment...
    – Nick
    Commented Nov 30, 2023 at 23:51
  • 5
    are you sure? there's (/will be) literally a flag reason for it: "Should be a question". cc. @Nick
    – starball
    Commented Dec 1, 2023 at 21:06

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .