You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
-16Lines changed: 0 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,19 +43,3 @@ You can also join the
43
43
44
44
Note that these are NOT for user tech support, and are moderated
45
45
for new users to prevent off-topic discussion.
46
-
47
-
# Support
48
-
49
-
## How to make a good bug report
50
-
51
-
* Make sure your bug is not a support issue.
52
-
Support issues should go to [the support forums](http://discuss.ardupilot.org/t/new-ardupilot-methodic-configurator-gui/115038/1) and
53
-
include a `.bin` log file and a `.zip` file with all the intermediate `.param` files if possible.
54
-
If you're not sure you have a bug, you should seek support first.
55
-
* Search for your bug, and make sure it is [not already reported](https://github.com/ArduPilot/MethodicConfigurator/issues).
56
-
If it is already reported, comment on that issue.
57
-
* Only report one bug per issue report.
58
-
* Write a clear and concise summary. Be specific about what component of the software you are writing about, and follow the convention: "Copter: blah blah blah"
59
-
* Write a clear and concise description, with **particularly clear steps** to reproduce the problem.
60
-
Include logs that display the bug. **Try to report only facts in your issue report, keeping your assumptions out of it.**
61
-
* The majority of issues open now are good or acceptable by these guidelines. Please refer to them for examples.
0 commit comments