2 replaced http://english.stackexchange.com/ with https://english.stackexchange.com/
source | link

I will propose a method to figure out whether it's okay to answer a gray-zone question. Feedback would be very welcome!

Suppose I read an iffy question that has received no answers yet. If it has at least one close-vote already, then don't write an answer, and wait and see if the question survives the challenge. Otherwise, evaluate the question to see if it is an obvious duplicate, poorly explained or documented, a proofreading request, or more suitable for ELL -- if so, vote to close with an appropriate reason. If not, it's okay to write an answer.

Example question: http://english.stackexchange.com/questions/361763/what-does-it-mean-by-lie-to-somethinghttps://english.stackexchange.com/questions/361763/what-does-it-mean-by-lie-to-something

enter image description here

By my proposed algorithm, it would not be frowned upon to write an answer to such a question.

I will propose a method to figure out whether it's okay to answer a gray-zone question. Feedback would be very welcome!

Suppose I read an iffy question that has received no answers yet. If it has at least one close-vote already, then don't write an answer, and wait and see if the question survives the challenge. Otherwise, evaluate the question to see if it is an obvious duplicate, poorly explained or documented, a proofreading request, or more suitable for ELL -- if so, vote to close with an appropriate reason. If not, it's okay to write an answer.

Example question: http://english.stackexchange.com/questions/361763/what-does-it-mean-by-lie-to-something

enter image description here

By my proposed algorithm, it would not be frowned upon to write an answer to such a question.

I will propose a method to figure out whether it's okay to answer a gray-zone question. Feedback would be very welcome!

Suppose I read an iffy question that has received no answers yet. If it has at least one close-vote already, then don't write an answer, and wait and see if the question survives the challenge. Otherwise, evaluate the question to see if it is an obvious duplicate, poorly explained or documented, a proofreading request, or more suitable for ELL -- if so, vote to close with an appropriate reason. If not, it's okay to write an answer.

Example question: https://english.stackexchange.com/questions/361763/what-does-it-mean-by-lie-to-something

enter image description here

By my proposed algorithm, it would not be frowned upon to write an answer to such a question.

1
source | link

I will propose a method to figure out whether it's okay to answer a gray-zone question. Feedback would be very welcome!

Suppose I read an iffy question that has received no answers yet. If it has at least one close-vote already, then don't write an answer, and wait and see if the question survives the challenge. Otherwise, evaluate the question to see if it is an obvious duplicate, poorly explained or documented, a proofreading request, or more suitable for ELL -- if so, vote to close with an appropriate reason. If not, it's okay to write an answer.

Example question: http://english.stackexchange.com/questions/361763/what-does-it-mean-by-lie-to-something

enter image description here

By my proposed algorithm, it would not be frowned upon to write an answer to such a question.