mirror of
https://github.com/YunoHost/doc.git
synced 2024-09-03 20:06:26 +02:00
56 lines
2.9 KiB
Markdown
56 lines
2.9 KiB
Markdown
---
|
|
title: Help me
|
|
template: docs
|
|
taxonomy:
|
|
category: docs
|
|
routes:
|
|
default: '/help-me'
|
|
---
|
|
|
|
Even though YunoHost contributors try to continuously perfect it, YunoHost itself or this documentation are not free from bugs or flaw. To let us help you, however, you need to follow these guidelines.
|
|
|
|
# Dos
|
|
|
|
## Be courteous and patient
|
|
Help in the chatrooms or on the forum is given by our users and contributors, all volunteers. You may be in a hurry, you may be exhausted by fruitless trials... Have a break, have a sip of your preferred soothing beverage, then continue reading. We need you in a good mindset to help you.
|
|
|
|
## Explain the context
|
|
Your request needs to be stated in a complete but concise way. Explain plainly what you want to achieve and in what manner it is not working for you.
|
|
|
|
## Show errors and logs
|
|
This is absolutely paramount if YunoHost or a command fails. It always explains why, through a single error code or a full wall of seemingly illegible text.
|
|
|
|
For the latter, YunoHost provides green "Share with YunoPaste" buttons when something fails or in the Services page of the webadmin. Click on it, it will open a new web page, and you can then share its URL.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If your issue is not related to an installation or upgrade process but instead is about an app failing load properly, ideally you can investigate with your browser console (opened with the F12 key): its Network tab can show you HTTP error codes (including the infamous 403, 404, 500...), and its Console can output errors too.
|
|
|
|
Screenshots are most welcome.
|
|
|
|
To guide you, on the forum you need to fill in the Support request template.
|
|
|
|
# Don'ts
|
|
|
|
## Avoid the infamous [XY Problem](https://xyproblem.info/)
|
|
In a nutshell, explain the root cause of your issue. You may share your attempted solution, but *why* you need that potential solution is more important.
|
|
|
|
## Do not be vague
|
|
Do not assume we understand what you are talking about, do not take shortcuts, do not rephrase, do not simplify, do not trim the error messages.
|
|
|
|
Do not write "it does not work", "it does not want", "it does not load", ["computer says no"](https://en.wikipedia.org/wiki/Computer_says_no).
|
|
|
|
Explain what is wrong, and how it is displayed onscreen. There is, for example, an important difference between a completely blank page and a blank page with a minimalistic error code.
|
|
|
|
## Directly ask your question
|
|
|
|
No need to ask if you can ask. It is a support chat/forum, therefore yes, you can ask your question.
|
|
|
|
Do not ask your question like a poll, as in "Did anyone managed to get app XY working?". If it is not working for you, then explain directly what issue you got, explain the context, share the logs.
|
|
|
|
|
|
## Do not be an asshole
|
|
Access to the forum or the chatrooms is a courtesy that can be revoked.
|