Return to Answer

###General outline / category list of things we could / should have:

• Shopping questions
• Localized troubleshooting questions (by contrast, canonical troubleshooting questions should not be closed)
• Questions about imminent future/speculative product releases that are not yet officially released (this does not include official public releases of beta or release candidate software) - should be closed because they're too localized to that point in time before the release, and the answers prior to release would only be speculative until the product itself is out. Note that this doesn't really apply to open source software, since someone can look in the VCS and see exactly what it's doing right now, but for closed source or hardware products, only an employee could confidently answer if the product is still "under wraps".
• Questions asking for someone to design a solution to a problem (we're not McSoftware's, as Tanner loves to say)

I am not good at making friendly, politically-neutral statements that can be understood by a 4th grader, so I will refrain from authoring actual quotes to put in our list that appear in a little box displayed to the user.

General outline / category list of things we could / should have:

• Shopping questions
• Localized troubleshooting questions (by contrast, canonical troubleshooting questions should not be closed)
• Questions about imminent future/speculative product releases that are not yet officially released (this does not include official public releases of beta or release candidate software) - should be closed because they're too localized to that point in time before the release, and the answers prior to release would only be speculative until the product itself is out. Note that this doesn't really apply to open source software, since someone can look in the VCS and see exactly what it's doing right now, but for closed source or hardware products, only an employee could confidently answer if the product is still "under wraps".
• Questions asking for someone to design a solution to a problem (we're not McSoftware's, as Tanner loves to say)

I am not good at making friendly, politically-neutral statements that can be understood by a 4th grader, so I will refrain from authoring actual quotes to put in our list that appear in a little box displayed to the user.

###General outline / category list of things we could / should have:

• Shopping questions
• Localized troubleshooting questions (by contrast, canonical troubleshooting questions should not be closed)
• Questions about imminent future/speculative product releases that are not yet officially released (this does not include official public releases of beta or release candidate software) - should be closed because they're too localized to that point in time before the release, and the answers prior to release would only be speculative until the product itself is out. Note that this doesn't really apply to open source software, since someone can look in the VCS and see exactly what it's doing right now, but for closed source or hardware products, only an employee could confidently answer if the product is still "under wraps".
• Questions asking for someone to design a solution to a problem (we're not McSoftware's, as Tanner loves to say)

I am not good at making friendly, politically-neutral statements that can be understood by a 4th grader, so I will refrain from authoring actual quotes to put in our list that appear in a little box displayed to the user.

###General outline / category list of things we could / should have:

• Shopping questions
• Localized troubleshooting questions (by contrast, canonical troubleshooting questions should not be closed)
• Questions about imminent future/speculative product releases that are not yet officially released (this does not include official public releases of beta or release candidate software) - should be closed because they're too localized to that point in time before the release, and the answers prior to release would only be speculative until the product itself is out. Note that this doesn't really apply to open source software, since someone can look in the VCS and see exactly what it's doing right now, but for closed source or hardware products, only an employee could confidently answer if the product is still "under wraps".
• Questions asking for someone to design a solution to a problem (we're not McSoftware's, as Tanner loves to say)

I am not good at making friendly, politically-neutral statements that can be understood by a 4th grader, so I will refrain from authoring actual quotes to put in our list that appear in a little box displayed to the user.