8
$\begingroup$

Custom close reasons have been live for a while now. We currently have 2 of the (3) given in use but a recent surge in questions being closed has prompted the need for a few more that are more tailored to address specific questions/close reasons instead of writing up why it is off-topic everytime.

Here are some guidelines to work with:

  • Keep it simple - so new users reading these will understand, especially if they are not familiar with StackExhange.
  • Give solid reasoning - try to have something that's not too open-ended as to open things up to a debate or retort.
  • Keep it brief - there's no need to write a book about it so lets aim for under 500 characters, including links and other Markdown tags.
  • Give your reasoning behind each reason - it helps to reference previous meta posts so we don't confuse users that haven't gotten the chance (or time) to peruse our meta site.

We are currently looking for close reasons pertaining to:

  • Not even remotely about Blender

    This question does not appear to be about Blender within the scope defined in the help center.

  • Too localized

    This question is too localized in its current form and is unlikely to be applicable outside of a very narrow context. Consider broadening the scope of this question in order to make it more useful for future users of the site.

  • Bug reports

    This question appears to be off-topic because it is a bug report and not an actual question. These should be reported to Blender's tracker instead.

  • Feature requests

  • Hardware questions
  • Unrelated programming questions (C/C++) etc

See What questions should be definitely off-topic? for more ideas on what is off-topic here.

$\endgroup$
  • 3
    $\begingroup$ We should also have a close reason to handle tutorial requests. This might normally be covered by the standard "no effort" StackExchange reason, but I think the nature of this site deserves a reason that's more clear and less frustrating to people who might not understand how their question "shows no effort." $\endgroup$ – Matt Dec 3 '13 at 16:52
  • $\begingroup$ @Matt I agree, hence the point of this post. Feel free to suggest some below. $\endgroup$ – iKlsR Dec 3 '13 at 16:55
  • $\begingroup$ The bug report one needs to be updated, that link goes to a 404 now that blender.org has been updated. $\endgroup$ – gandalf3 Dec 13 '13 at 9:52
  • $\begingroup$ We should use all top three. Feature requests off-topic reason doesn't seem that necessary. $\endgroup$ – Daniel Pendergast Dec 15 '13 at 19:21
  • $\begingroup$ @DantheMan We want specific close reasons. Doesn't make sense to close then have to further explain why. $\endgroup$ – iKlsR Dec 15 '13 at 20:18
  • $\begingroup$ @iKlsR I thought there was a limit to how many off-topic reasons of 3. $\endgroup$ – Daniel Pendergast Jan 3 '14 at 14:51
  • $\begingroup$ @DantheMan We can ask for more. SO has like a dozen or so. $\endgroup$ – iKlsR Jan 3 '14 at 15:06
6
$\begingroup$

Tutorial Requests

This question appears to be off-topic because it requires step-by-step instructions for a process that is specific to a particular project, and/or demonstrates too little effort on the part of the asker. These kinds of problems have been well solved elsewhere and are beyond the scope of this StackExchange.

$\endgroup$
4
$\begingroup$

Source code questions

This question appears to be off-topic because it is about Blender C/C++ source code. These questions are considered outside the scope of this StackExchange as defined in the help center. Development questions should be asked of the developers directly instead, see the contacting developers page of the blender wiki.

$\endgroup$
4
$\begingroup$

Feature Requests

This question appears to be off-topic because it asks about adding features not yet in Blender. These should instead be posted on the requests section of the blender wiki or in the bf-functionality mailing list.

$\endgroup$
  • 3
    $\begingroup$ Would this apply to people asking if such a feature exists in Blender or only if they asking for the developers to implement it? $\endgroup$ – Daniel Pendergast Jan 14 '14 at 20:08
  • 1
    $\begingroup$ @DantheMan See meta.blender.stackexchange.com/q/177/599 "Someone can ask if a feature exists to perform a certain task, but unless its in a blender release, or already implemented to be included in the next release - I think the answer has to be NO." $\endgroup$ – gandalf3 Jan 15 '14 at 7:29
4
$\begingroup$

Hardware/OS questions

This questions appears to be off-topic because it is about the operating system, hardware, performance, or compatibility. These questions are considered off-topic because there is often no definitive answer, so they tend to require too much discussion to be suitable for Q&A format. Try asking on BlenderArtists for support instead.

$\endgroup$
  • $\begingroup$ I think we can... $\endgroup$ – iKlsR Dec 13 '13 at 11:39
  • $\begingroup$ Should this close reason be generalized to include platform/driver related questions? $\endgroup$ – gandalf3 Mar 1 '14 at 20:05
  • $\begingroup$ Yes, it's out of the scope of this site. $\endgroup$ – iKlsR Mar 1 '14 at 20:36
2
$\begingroup$

Bug Reports for Code by Independent Authors

I think there should be two different Bug report close reasons:

  • One for bugs in Blender itself: that one should say "report to Blender's Bug tracker"

  • One for bugs in code from other coders: that one should say "report to code author"

I think this is a very important distinction that OP needs to be aware of, because if we refer bug reports about non-Blender code to the Blender devs, they're going to get upset with us if it keeps happening.

$\endgroup$
-1
$\begingroup$

Bug Reports

This can also count for technical support for things like crashes.

$\endgroup$

You must log in to answer this question.

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