Asking for help: Difference between revisions

Jump to navigation Jump to search
Moving sections around; +section about asking for help on the wiki
m (→‎Before asking for help: Grammar/rephrasing for clarity)
(Moving sections around; +section about asking for help on the wiki)
Line 16: Line 16:
#* Try a Google search
#* Try a Google search


== Asking for help ==
== Where to ask for help ==
=== Getting the attention ===
The best way to get attention is often to:
 
* Make it as easy as possible to figure out what you need help with.
* Show that you have tried to solve the problem yourself first, and how.
* Be honest about the problem (in essence do not exaggerate).
* Try provide a sufficient amount of information, while at the same time being concise.
 
Depending on what kind of problem you have, you probably will have to supply us with some information about your computer in addition to information about the problem you are experiencing.  As we do not have access to your computer, you need to be our eyes and ears.
 
Even if some of the information we ask for is not always required in order to fix a particular issue, it can often simplify shorten the troubleshooting process, for example by allowing us to exclude certain problem sources.  Therefore, if at all possible please try to provide any information requested.
 
If anything is unclear, or you do not know how to obtain certain information, please ask for clarification rather than ignoring a particular request.
 
=== Keeping the attention ===
You can expect some follow up questions, in particular regarding reports about probable bugs.  It is literally essential that they can be reproduced by the other user or developer.
 
Often a problem or a bug can be solved quickly as soon as it can reliably be reproduced.
 
== Where to ask ==
Depending on the nature of your problem, different places are better suited to ask your question at.
Depending on the nature of your problem, different places are better suited to ask your question at.


Line 42: Line 22:


=== The FlightGear forum ===
=== The FlightGear forum ===
* [http://forum.flightgear.org/index.php The FlightGear forum]
* [http://forum.flightgear.org/index.php FlightGear forum]


The forum is the right place to ask if you have questions related to:
The forum is the right place to ask if you have questions related to:
Line 58: Line 38:


=== The developer mailing list ===
=== The developer mailing list ===
* [http://sourceforge.net/p/flightgear/mailman/flightgear-devel/ The developer mailing list]
* [http://sourceforge.net/p/flightgear/mailman/flightgear-devel/ Developer mailing list]


If you are able to [[Building FlightGear|build FlightGear]] from source, or even [[TerraGear]] and have questions related to that or to issues with them, you may be better served by asking for help at the developer mailing list.
If you are able to [[Building FlightGear|build FlightGear]] from source, or even [[TerraGear]] and have questions related to that or to issues with them, you may be better served by asking for help at the developer mailing list.


=== The issue tracker ===
=== The issue tracker ===
* {{tickets|The issue tracker}}
* {{tickets|Issue tracker}}


Usually it is a good idea to ask for help in the other places before reporting a bug.
Usually it is a good idea to ask for help in the other places before reporting a bug.
=== The wiki ===
Depending on what you are asking about different places would be the right to ask for help:
* About the FlightGear wiki in general the the right place to ask is [[FlightGear wiki:Village Pump|Village pump]].
* About a specific page the discussion page of that page is the right place to ask (Click the ''Discussion'' tab above the page).
* About edits by a specific user the right place to ask is the user discussion page, <code>User talk:''User name''</code>, is the right place to ask.
== Asking for help ==
=== Getting the attention ===
The best way to get attention is often to:
* Make it as easy as possible to figure out what you need help with.
* Show that you have tried to solve the problem yourself first, and how.
* Be honest about the problem (in essence do not exaggerate).
* Try provide a sufficient amount of information, while at the same time being concise.
Depending on what kind of problem you have, you probably will have to supply us with some information about your computer in addition to information about the problem you are experiencing.  As we do not have access to your computer, you need to be our eyes and ears.
Even if some of the information we ask for is not always required in order to fix a particular issue, it can often simplify shorten the troubleshooting process, for example by allowing us to exclude certain problem sources.  Therefore, if at all possible please try to provide any information requested.
If anything is unclear, or you do not know how to obtain certain information, please ask for clarification rather than ignoring a particular request.
=== Keeping the attention ===
You can expect some follow up questions, in particular regarding reports about probable bugs.  It is literally essential that they can be reproduced by the other user or developer.
Often a problem or a bug can be solved quickly as soon as it can reliably be reproduced.


== Making proper issue reports ==
== Making proper issue reports ==

Navigation menu