Forum communication: Difference between revisions

Jump to navigation Jump to search
m
http://forum.flightgear.org/viewtopic.php?f=8&t=22728&p=206674#p206657
(initial draft)
 
m (http://forum.flightgear.org/viewtopic.php?f=8&t=22728&p=206674#p206657)
Line 1: Line 1:
So you have a problem with using FG, and someone pointed you here. Please take the time to read on.
So you have a problem with installing/starting/using FG, and someone pointed you here. Please take the time to read on.


FG doesn't rely on sales or license fees. FG relies on having a base of contributors, but in order to contribute, people need to be able to see something that bothers them not as something to complain about but as something to be investigated, understood and fixed.
FG doesn't rely on sales or license fees. FG relies on having a base of contributors usually volunteering their time, but in order to contribute, people need to be able to see something that bothers them not as something to complain about but as something to be investigated, understood and fixed.


Misunderstandings may arise during a forum discussion. After all, most people here aren't native English speakers. But fighting on the forums is just a huge waste of time and energy. That time is better spend on what our developers enjoy: creating software. They are willing to help ''if provided with enough information'' on the problem at hand. Otherwise they wouldn't hang out on the forum. And they are not getting payed.
Most of us enjoy understanding complex problems, and even fixing bugs - but typically a bug that you may encounter may very well never show up for people involved in developing/contributing to FlightGear. This is why you need to be our eyes and ears - we cannot see what you're seeing, and we cannot know what you have done.
 
Remotely troubleshooting problems is an extremely tedious process, that gets more tricky because of people's tendency to act in a frustrated and disrespectful way.
 
Misunderstandings may arise during a forum discussion. After all, most people here aren't native English speakers. But fighting on the forums is just a huge waste of time and energy. That time is better spent on what our developers enjoy: creating software and new features. They are willing to help ''if provided with enough information'' on the problem at hand. Otherwise they wouldn't hang out on the forum. And they are not getting paid.


'''Remember: you're the one having a problem with FG. You're asking for help, and you're not paying for the service.''' So,
'''Remember: you're the one having a problem with FG. You're asking for help, and you're not paying for the service.''' So,
Line 11: Line 15:
# Try hard to provide the information you are asked for.
# Try hard to provide the information you are asked for.
# If you are pointed to, e.g., the wiki articles, carefully read and try to understand them.
# If you are pointed to, e.g., the wiki articles, carefully read and try to understand them.
# Work through any suggested steps to troubleshoot the problem further
# If you hit any roadblocks, tell us exactly how far you proceeded and where you needed help
# If you are not sure how to provide good feedback, better provide as much info as possible - i.e. through screen shots or youtube videos
# don't expect immediate responses, sometimes it may take a few days to get back to you, especially during busy times (release preparations)
# try to be respectful, deal with others the way you want to be dealt with


You may of course disagree with someone who is most lkely way more experienced with FG than you are. But more often than not you'll be wrong.
You may of course disagree with someone who is most likely way more experienced with FG than you are. But more often than not you'll be wrong.
Keep in mind that there's really only a handful of people on the forum who regularly provide support to newcomers, those are usually also the most knowledgeable people - and unfortunately, those are also the ones who are most likely to be busy with other aspects of FlightGear.


Further reading:
Further reading:
[[How_the_FlightGear_project_works]]
* [[How_the_FlightGear_project_works]]
* [[Troubleshooting Problems]]

Navigation menu