3 Please remember the issue tracker on github is _not_ for user support. Please also do not email developers directly for support. Instead please use IRC or the forums first, Also read through the wiki for guidance. Then if the problem is confirmed create an issue that details how to repeat the problem so it can be investigated.
5 Issues created without steps to repeat are likely to be closed. E-mail requests for support will go un-answered; All support needs to be public so that other people can read the problems and solutions.
7 Remember that issues that are due to mis-configuration, wiring or failure to read documentation just takes time away from the developers and can often be solved without developer interaction by other users.
9 Please search for existing issues *before* creating new ones.
11 When submitting an issue the general rule is to include:
13 1. What is your setup and a detailed explanation of the issue, also include last working version of INAV.
14 1. status dump from cli.
15 1. bootlog dump from cli.
16 1. dump dump from cli.
17 1. BLACKBOX log of the issue.
21 Please refer to the development section in the `docs/development` folder.