Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Guidelines for asking

On this site, it's reasonably straightforward to upvote or downvote questions, or ask for corrections or clarification. But how do I decide what counts as a good question or a bad question?

From what I could find, the closest thing to guidelines is at https://wiki.documentfoundation.org/Ask/Getting_Started. Also, this answer gives links to a different site.

For example, consider the question at https://ask.libreoffice.org/en/question/133291/how-can-i-get-text-back-since-i-only-have-notepad-with-your-software/#133324. It seems like a bad question for many reasons:

  • title is too long and doesn't seem like a summary
  • no version number or operating system
  • not clear what file types are involved
  • no reproducible steps were given
  • The whole question is very unclear.

However, I did not downvote because I cannot point to any recognized standard that was not followed.

Here is a suggested list.

  • Research the problem online first to avoid duplication. Mention what you find.
  • Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques.
  • Describe problems encountered, with complete error messages and line numbers of code if relevant.
  • Give all information and steps necessary to reproduce the problem. Attach a sample document if necessary.
  • Provide version, operating system and locale when relevant.
  • Clearly state the actual question and desired results.
  • Use common grammar and wording so that people in other countries besides your own can understand.
  • Title should be a short summary and include relevant tags. Do not check community wiki for normal questions.
  • After asking, monitor the question for a few days in case corrections are requested. Edit the question if needed.
  • If a useful answer is given, mark it as correct and consider upvoting. Otherwise, explain in comments why the answer does not work.

Guidelines for asking

On this site, it's reasonably straightforward to upvote or downvote questions, or ask for corrections or clarification. But how do I decide what counts as a good question or a bad question?

From what I could find, the closest thing to guidelines is at https://wiki.documentfoundation.org/Ask/Getting_Started. Also, this answer gives links to a different site.

For example, consider the question at https://ask.libreoffice.org/en/question/133291/how-can-i-get-text-back-since-i-only-have-notepad-with-your-software/#133324. It seems like a bad question for many reasons:

  • title is too long and doesn't seem like a summary
  • no version number or operating system
  • not clear what file types are involved
  • no reproducible steps were given
  • The whole question is very unclear.

However, I did not downvote because I cannot point to any recognized standard that was not followed.

Here is a suggested list.

  • Research the problem online first to avoid duplication. Mention what you find.
  • Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques.
  • Describe problems encountered, with complete error messages and line numbers of code if relevant.
  • Give all information and steps necessary to reproduce the problem. Attach a sample document if necessary.
  • Provide version, operating system and locale when relevant.
  • Clearly state the actual question and desired results.
  • Use common grammar and wording so that people in other countries besides your own can understand.
  • Title should be a short summary and include relevant tags. Do not check community wiki for normal questions.
  • After asking, monitor the question for a few days in case corrections are requested. Edit the question if needed.
  • If a useful answer is given, mark it as correct and consider upvoting. Otherwise, explain in comments why the answer does not work.

Guidelines for asking

On this site, it's reasonably straightforward to upvote or downvote questions, or ask for corrections or clarification. But how do I decide what counts as a good question or a bad question?

From what I could find, the closest thing to guidelines is at https://wiki.documentfoundation.org/Ask/Getting_Started. Also, this answer gives links to a different site.

For example, consider the question at https://ask.libreoffice.org/en/question/133291/how-can-i-get-text-back-since-i-only-have-notepad-with-your-software/#133324. https://ask.libreoffice.org/en/question/133291/how-can-i-get-text-back-since-i-only-have-notepad-with-your-software. It seems like a bad question for many reasons:

  • title is too long and doesn't seem like a summary
  • no version number or operating system
  • not clear what file types are involved
  • no reproducible steps were given
  • The whole question is very unclear.

However, I did not downvote because I cannot point to any recognized standard that was not followed.

Guidelines for asking

On this site, it's reasonably straightforward to upvote or downvote questions, or ask for corrections or clarification. But how do I decide what counts as a good question or a bad question?

From what I could find, the closest thing to guidelines is at https://wiki.documentfoundation.org/Ask/Getting_Started. Also, this answer gives links to a different site.

For example, consider the question at https://ask.libreoffice.org/en/question/133291/how-can-i-get-text-back-since-i-only-have-notepad-with-your-software. It seems like a bad question for many reasons:

  • title is too long and doesn't seem like a summary
  • no version number or operating system
  • not clear what file types are involved
  • no reproducible steps were given
  • The whole question is very unclear.

However, I did not downvote because I cannot point to any recognized standard that was not followed.

Guidelines for asking

On this site, it's reasonably straightforward to upvote or downvote questions, or ask for corrections or clarification. But how do I decide what counts as a good question or a bad question?

From what I could find, the closest thing to guidelines is at https://wiki.documentfoundation.org/Ask/Getting_Started. Also, this answer gives links to a different site.

For example, consider the question at https://ask.libreoffice.org/en/question/133291/how-can-i-get-text-back-since-i-only-have-notepad-with-your-software. It seems like a bad question for many reasons:

  • title is too long and doesn't seem like a summary
  • no version number or operating system
  • not clear what file types are involved
  • no reproducible steps were given
  • The whole question is very unclear.

However, I did not downvote because I cannot point to any recognized standard that was not followed.

Guidelines for asking

On this site, it's reasonably straightforward to upvote or downvote questions, or ask for corrections or clarification. But how do I decide what counts as a good question or a bad question?

From what I could find, the closest thing to guidelines is at https://wiki.documentfoundation.org/Ask/Getting_Started. Also, this answer gives links to a different site.

For example, consider the question at https://ask.libreoffice.org/en/question/133291/how-can-i-get-text-back-since-i-only-have-notepad-with-your-software. It seems like a bad question for many reasons:

  • title is too long and doesn't seem like a summary
  • no version number or operating system
  • not clear what file types are involved
  • no reproducible steps were given
  • The whole question is very unclear.

However, I did not downvote because I cannot point to any recognized standard that was not followed.

Guidelines for asking

On this site, it's reasonably straightforward to upvote or downvote questions, or ask for corrections or clarification. But how do I decide what counts as a good question or a bad question?

From what I could find, the closest thing to guidelines is at https://wiki.documentfoundation.org/Ask/Getting_Started. Also, this answer gives links to a different site.

For example, consider the question at https://ask.libreoffice.org/en/question/133291/how-can-i-get-text-back-since-i-only-have-notepad-with-your-software. It seems like a bad question for many reasons:

  • title is too long and doesn't seem like a summary
  • no version number or operating system
  • not clear what file types are involved
  • no reproducible steps were given
  • The whole question is very unclear.

However, I did not downvote because I cannot point to any recognized standard that was not followed.

click to hide/show revision 8
None

Guidelines for asking

On this site, it's reasonably straightforward to upvote or downvote questions, or ask for corrections or clarification. But how do I decide what counts as a good question or a bad question?

From what I could find, the closest thing to guidelines is at https://wiki.documentfoundation.org/Ask/Getting_Started. Also, this answer gives links to a different site.

For example, consider the question at https://ask.libreoffice.org/en/question/133291/how-can-i-get-text-back-since-i-only-have-notepad-with-your-software. It seems like a bad question for many reasons:

  • title is too long and doesn't seem like a summary
  • no version number or operating system
  • not clear what file types are involved
  • no reproducible steps were given
  • The whole question is very unclear.

However, I did not downvote because I cannot point to any recognized standard that was not followed.

click to hide/show revision 9
None

Guidelines for asking

On this site, it's reasonably straightforward to upvote or downvote questions, or ask for corrections or clarification. But how do I decide what counts as a good question or a bad question?

From what I could find, the closest thing to guidelines is at https://wiki.documentfoundation.org/Ask/Getting_Started. Also, this answer gives links to a different site.

For example, consider the question at https://ask.libreoffice.org/en/question/133291/how-can-i-get-text-back-since-i-only-have-notepad-with-your-software. It seems like a bad question for many reasons:

  • title is too long and doesn't seem like a summary
  • no version number or operating system
  • not clear what file types are involved
  • no reproducible steps were given
  • The whole question is very unclear.

However, I did not downvote because I cannot point to any recognized standard that was not followed.

click to hide/show revision 10
None

Guidelines for asking

On this site, it's reasonably straightforward to upvote image descriptionor downvote image descriptionquestions, or ask for corrections or clarification. clarification image description.

But how do I decide what counts as a good question or a bad question?

From what I could find, the closest thing to guidelines is at https://wiki.documentfoundation.org/Ask/Getting_Started. Also, this answer gives links to a different site.

For example, consider the question at https://ask.libreoffice.org/en/question/133291/how-can-i-get-text-back-since-i-only-have-notepad-with-your-software. It seems like a bad question for many reasons:

  • title is too long and doesn't seem like a summary
  • no version number or operating system
  • not clear what file types are involved
  • no reproducible steps were given
  • The whole question is very unclear.

However, I did not downvote because I cannot point to any recognized standard that was not followed.