16

From some brief comments in AD Chat, it appears we currently have one spare slot for a new close reason.

I would like to propose a 'zero research' type reason - though I'm open to suggestions on the precise wording.

grgarside mentioned that he already has a standard comment he uses for 'no research on code/applescript' type questions...

Questions asking for code must demonstrate a minimal understanding of the problem being solved. Include attempted solutions, why they didn't work, and the expected results.

which I think is fine for that specific case, but I think we need something more generic to cover the 'really didn't bother' questions on all topics.

The How to Ask page is already the best place to point these, as research is the opening section, but we have just the already very broad Basic Customer Support close reason pointing to it, which I don't think we need to add more sub-clauses to.

I'm assuming it would need to go in the off-topic closure, which feels a bit odd, but if customer support fits there, then I guess no research could too.

I propose something along the lines of

Questions must demonstrate a reasonable amount of research & understanding of the problem being solved. Please edit to clearly describe your problem and the research done so far to solve it, including attempted solutions, why they didn't work, and the expected results.

which is, of course, borrowing heavily from the above.

The floor is open for better suggestions.

Pic of CS close added, just for easy ref & so we can see how it actually looks in situ, rather than just the text.

enter image description here

Edit 29 May:

I'm going to keep adding zero effort examples as I find them...

Combine/merge two separate image files of the same thing(newspaper page) taken in half

  • 1
    Thanks! May I encourage you to post your proposal as a first answer so that people can vote on the text? – nohillside May 22 '17 at 11:14
  • @patrix - sure thing... – Tetsujin May 22 '17 at 11:26
  • I like where you're going with this, but can I just clarify where the one remaining slot is for closing questions? Is it on the first screen you get when you first go to close a question (i.e. the one listing 5 options, starting with duplicate of... and finishing with primarily opinion-based? Or is it on the Off-Topic screen instead (i.e. the one listing 4 options, starting with Basic Customer Support.... etc? – Monomeeth May 22 '17 at 12:09
  • Honestly, idk. @patrix mentioned it in Chat - "We do have one custom close reason left. If you want to pitch for it, please raise it on Meta" so hopefully he can fill us in on the details. – Tetsujin May 22 '17 at 12:18
  • @Monomeeth We can define up to three site-specific "Off Topic" close reasons (in addition to the standard ones for migration and "other"). Of these three there are currently only two in use. – nohillside May 22 '17 at 12:47
  • Generally speaking it might take some effort to clearly differentiate between the already existing "Customer Support" reason and the one proposed here. I have the feeling that they are indeed different, but we may need to reword the "Customer Support" reason as well to make the distinction more obvious. – nohillside May 22 '17 at 12:49
  • I've always actually thought the customer support one is a bit 'busy', trying to cover too much in one go. I guess it does partly cover the no research area - but it lumps CS in with 'opinionated' rather clumsily. I'm adding a pic of the CS close to my question for easy reference. perhaps this needs a revamp, in tandem with adding a new one?? – Tetsujin May 22 '17 at 12:52
  • I agree! I've always felt the Customer support reason was somewhat clumsy. I think it could definitely do with an edit. – Monomeeth May 22 '17 at 12:57
  • Essentially, if we leave the 'coding == SO' as it is, then we have 3 close reasons we need to squeeze into the space for 2... CS, shopping & no research. That might take some skilled wording. – Tetsujin May 22 '17 at 13:02
  • 1
    There are two types of coding questions: clearly off-topic ones (ObjC or Swift coding issue) and badly researched on-topic ones (AppleScript, shell scripts and such). The latter one fits onto the "no research" category and may need to be reflected in the wording somehow. – nohillside May 22 '17 at 13:26
  • I sure wish we had this on electronics.stackexchange.com. So many homework questions without effort. – Brian Carlton May 27 '17 at 22:25
  • @BrianCarlton can you believe that there are sites that have that close reason and want to get rid of it? – Glorfindel Jun 2 '17 at 11:26
  • Very related status-declined Meta SE post: Introduce a “general reference” close reason, also see links in the related blog post Are Some Questions Too Simple? discussions in other sites. – muru Jun 5 '17 at 5:09
16

Proposal ported to answer space for voting purposes/comments...

Questions must demonstrate a reasonable amount of research & understanding of the problem being solved. Please edit to clearly describe your problem and the research done so far to solve it, including attempted solutions, why they didn't work, and the expected results.

  • 9
    +1 I like this. If I was going to change anything, it would only be to add something like This will help the community to better provide a good answer to your problem. – Monomeeth May 22 '17 at 12:55
  • 1
    Great way to make this clear for votes. I"m tempted to first split the "basic troubleshooting" from the "off site resource" close reason first though. – bmike May 23 '17 at 10:41
  • This may require further refinement, for sure. It was essentially a punt in the right direction rather than an attempt to fix it all in one go. Perhaps it can be resolved in comments/potential answers, then a final "this is what's going to happen" answer put in at the end... – Tetsujin May 23 '17 at 20:19
8

We currently have a a whole bunch of things mixed into the custom close reasons

  • Questions about software development
  • Basic customer support questions (where the question should first go to the vendor, as described in Why we're not customer support for [company X or product Y]
  • Recommend or find stuff (aka "please google for me")
  • Questions which don't show any research done, are basically "write this script for me" and similar (which often are hard to distinguish from "unclear what you are asking" or "too broad" type of question)

This basically means that we have four different (but not totally unrelated) things squeezed into three close reasons. Which obviously doesn't work out so well sometimes.

One way forward would be to rely more on the fact that we already have meta posts explaining the reasoning behind the basic customer support and the recommendation close reason and use this to keep the close reason to the point. So we could go with

  • Questions must demonstrate a reasonable amount of research & understanding of the problem being solved. Please edit to clearly describe your problem and the research done so far to solve it, including attempted solutions, why they didn't work, and the expected results.
  • Basic customer support questions and questions asking to recommend or find a Mac, book, tool, tutorial or other off-site resource are off-topic. Please refer to the information in the appropriate post linked above for details on how to proceed. If applicable you can edit your question and have the hold reviewed.
  • Questions about software development are off-topic here, but can be asked on Stack Overflow

We may need to have an AD-specific version of the recommendation meta-post for this, but that's something we can tackle if we agree on going with these three reasons.

  • That's looking good so far, for me. Removing the opinion/spam doesn't hurt at all imo & allows for both reasons to be more easily combined. – Tetsujin May 26 '17 at 10:02
  • Just a note - in the interim I'm VTC things like this as Too Broad - apple.stackexchange.com/questions/285225/… – Tetsujin May 30 '17 at 7:17
7

I'm tempted to try and roll this in to the Basic Customer support close reason. That close reason isn't here, so you can use this and other in the mean time:

I'm voting to close this question as off-topic because it's a Basic Customer support question. Please see the meta post linked above for details on how to proceed if you can edit the post and have the hold reviewed.

We currently have these two custom options:

The Basic Customer Support wording is removed from the "off site" resource close reason since people felt odd choosing it when both didn't apply as well as people with closed questions didn't get that they had to only fix half of the problems - not address both "support" and "research" constraints.

Since we only get three custom close reasons - do we still need this second "not enough research" reason?

I could see adding some of the proposed wording here to "basic customer support" close reason so we have used all 3 of 3 custom close reasons.

  • I'm with you so far - but it's shining examples like these - apple.stackexchange.com/questions/284653/… & apple.stackexchange.com/questions/284650/… which are classics in their own right. 1st is truly clueless, 2nd is definitely CS. I'd struggle to VTC the first as CS. It could go down as 'unclear', I guess. – Tetsujin May 24 '17 at 6:56
  • 1
    Ahhh... a late thought... can we customise the 'unclear' to include zero research? Thoughts? – Tetsujin May 24 '17 at 6:59
  • @Tetsujin We can't change the 'unclear what you are asking' reason just for AD – nohillside May 26 '17 at 7:34
  • @patrix - I had my suspicions it wouldn't be a moddable parameter. – Tetsujin May 26 '17 at 7:56

You must log in to answer this question.

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