ardupilot/.github/CONTRIBUTING.md

# How to contribute to the APM project?

If you are reading this page, you are possibly interested in contributing to our project.  We have a very active (and friendly) developer group and would love to have the help!  Possible ways you can help:

* Testing the code
* Filing issues on github, when you see a problem (or adding detail to existing issues that effect you)
* Fixing issues
* Adding new features
* Reviewing existing pull requests, and notifying the maintainer if it passes your code review.

# How to make a good bug report...

* Make sure your bug is not a support issue. Support issues should go to [the APM forums](http://discuss.ardupilot.org). Support issues with logs attached should generally go to the "Log files, Tuning, and Analysis of Log files" section. If you're not sure you have a bug, you should seek support first.
* Search for your bug, make sure it is not already reported. If it is already reported, make a comment on that issue.
* Only report one bug per issue report.
* 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"
* Write a clear and concise description, with **particularly clear steps** to reproduce the problem. Include logs that display the bug. **Try to report only facts in your issue report, keeping your assumptions out of it.** 
* The majority of issues open now are good or acceptable by these guidelines. Please refer to them for examples.

# Submitting patches

Please see our [wiki article](http://dev.ardupilot.org/wiki/submitting-patches-back-to-master/).

# Development Team

The ArduPilot project is open source and [maintained](https://github.com/ArduPilot/ardupilot#maintainers) by a team of volunteers.

To contribute, you can send a pull request on Github. You can also
join the [development discussion on Google
Groups](https://groups.google.com/forum/?fromgroups#!forum/drones-discuss). Note
that the Google Groups mailing lists are NOT for user tech support,
and are moderated for new users to prevent off-topic discussion.
documentation: Add a contributing & maintainers file Per our devcall last week. Adding now mainly so we can start pointing LogAnalyzer fixes to @chapman and quickly get them into master. @tridge & @randy - I kinda guessed at the maintainers list, we can update later as needed. 2014-07-06 15:32:03 -03:00			`# How to contribute to the APM project?`

			`If you are reading this page, you are possibly interested in contributing to our project. We have a very active (and friendly) developer group and would love to have the help! Possible ways you can help:`

			`* Testing the code`
			`* Filing issues on github, when you see a problem (or adding detail to existing issues that effect you)`
			`* Fixing issues`
			`* Adding new features`
			`* Reviewing existing pull requests, and notifying the maintainer if it passes your code review.`

			`# How to make a good bug report...`

Github: Add and update github templates 2016-04-11 21:31:13 -03:00			`* Make sure your bug is not a support issue. Support issues should go to [the APM forums](http://discuss.ardupilot.org). Support issues with logs attached should generally go to the "Log files, Tuning, and Analysis of Log files" section. If you're not sure you have a bug, you should seek support first.`
Update CONTRIBUTING.md 2014-10-12 03:46:42 -03:00			`* Search for your bug, make sure it is not already reported. If it is already reported, make a comment on that issue.`
Update CONTRIBUTING.md 2014-10-12 04:11:30 -03:00			`* Only report one bug per issue report.`
			`* 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"`
			`* Write a clear and concise description, with particularly clear steps to reproduce the problem. Include logs that display the bug. Try to report only facts in your issue report, keeping your assumptions out of it.`
Update CONTRIBUTING.md 2014-10-12 03:46:42 -03:00			`* The majority of issues open now are good or acceptable by these guidelines. Please refer to them for examples.`
documentation: Add a contributing & maintainers file Per our devcall last week. Adding now mainly so we can start pointing LogAnalyzer fixes to @chapman and quickly get them into master. @tridge & @randy - I kinda guessed at the maintainers list, we can update later as needed. 2014-07-06 15:32:03 -03:00
			`# Submitting patches`

Revising ardupilot.com to .org Revising ardupilot.com to .org 2016-04-23 17:45:02 -03:00			`Please see our [wiki article](http://dev.ardupilot.org/wiki/submitting-patches-back-to-master/).`
documentation: Add a contributing & maintainers file Per our devcall last week. Adding now mainly so we can start pointing LogAnalyzer fixes to @chapman and quickly get them into master. @tridge & @randy - I kinda guessed at the maintainers list, we can update later as needed. 2014-07-06 15:32:03 -03:00
			`# Development Team`

updated contributors url. Was pointing at missing file, now its at landing page url 2016-06-16 13:37:51 -03:00			`The ArduPilot project is open source and [maintained](https://github.com/ArduPilot/ardupilot#maintainers) by a team of volunteers.`
documentation: Add a contributing & maintainers file Per our devcall last week. Adding now mainly so we can start pointing LogAnalyzer fixes to @chapman and quickly get them into master. @tridge & @randy - I kinda guessed at the maintainers list, we can update later as needed. 2014-07-06 15:32:03 -03:00
			`To contribute, you can send a pull request on Github. You can also`
			`join the [development discussion on Google`
			`Groups](https://groups.google.com/forum/?fromgroups#!forum/drones-discuss). Note`
			`that the Google Groups mailing lists are NOT for user tech support,`
Update CONTRIBUTING.md 2014-10-12 03:46:42 -03:00			`and are moderated for new users to prevent off-topic discussion.`