Skip to content
Snippets Groups Projects
  • C-Glick's avatar
    e152011b
    Merge glick_dev_branch: · e152011b
    C-Glick authored
    Imported crazyflie firmware
    Squashed commit of the following:
    
    commit ede806b7
    Author: C-Glick <colton.glick@gmail.com>
    Date:   Thu Nov 11 19:55:37 2021 -0600
    
        update crazyflie submodules
    
    commit 0c732307
    Author: C-Glick <colton.glick@gmail.com>
    Date:   Thu Nov 11 19:43:20 2021 -0600
    
        imported CrazyFlie firmware
    
    commit 902ebde0
    Author: C-Glick <colton.glick@gmail.com>
    Date:   Tue Oct 19 20:43:28 2021 -0500
    
        Converted documentation folder into wiki submodule
    
    commit cbec1f2a
    Author: C-Glick <colton.glick@gmail.com>
    Date:   Tue Oct 19 20:17:22 2021 -0500
    
        Added wiki submodule to correct folder
    
    commit bdb4a4d8
    Author: crglick <crglick@iastate.edu>
    Date:   Wed Oct 20 01:14:10 2021 +0000
    
        Revert "Added wiki submodule"
    
        This reverts commit fc974d96
    
    commit fc974d96
    Author: C-Glick <colton.glick@gmail.com>
    Date:   Tue Oct 19 19:54:33 2021 -0500
    
        Added wiki submodule
    
    commit db390530
    Author: crglick <crglick@iastate.edu>
    Date:   Fri Oct 15 15:37:54 2021 -0500
    
        Updated website deploy script with correct address
    e152011b
    History
    Merge glick_dev_branch:
    C-Glick authored
    Imported crazyflie firmware
    Squashed commit of the following:
    
    commit ede806b7
    Author: C-Glick <colton.glick@gmail.com>
    Date:   Thu Nov 11 19:55:37 2021 -0600
    
        update crazyflie submodules
    
    commit 0c732307
    Author: C-Glick <colton.glick@gmail.com>
    Date:   Thu Nov 11 19:43:20 2021 -0600
    
        imported CrazyFlie firmware
    
    commit 902ebde0
    Author: C-Glick <colton.glick@gmail.com>
    Date:   Tue Oct 19 20:43:28 2021 -0500
    
        Converted documentation folder into wiki submodule
    
    commit cbec1f2a
    Author: C-Glick <colton.glick@gmail.com>
    Date:   Tue Oct 19 20:17:22 2021 -0500
    
        Added wiki submodule to correct folder
    
    commit bdb4a4d8
    Author: crglick <crglick@iastate.edu>
    Date:   Wed Oct 20 01:14:10 2021 +0000
    
        Revert "Added wiki submodule"
    
        This reverts commit fc974d96
    
    commit fc974d96
    Author: C-Glick <colton.glick@gmail.com>
    Date:   Tue Oct 19 19:54:33 2021 -0500
    
        Added wiki submodule
    
    commit db390530
    Author: crglick <crglick@iastate.edu>
    Date:   Fri Oct 15 15:37:54 2021 -0500
    
        Updated website deploy script with correct address
After you've reviewed these contribution guidelines, you'll be all set to contribute to this project.

Contributing

:thumbsup::tada: Thanks a lot for considering contributing :tada::thumbsup:

We welcome and encourage contribution. There is many way to contribute: you can write bug report, contribute code or documentation. You can also go to the bitcraze forum and help others.

Reporting issues

When reporting issues the more information you can supply the better.

  • Information about the environment:
    • What version of the firmware are you running
    • If relevant, what are you using to control the Crazyflie. ie. What lib or client, and what version.
  • How to reproduce the issue: Step-by-step guide on how the issue can be reproduced (or at least how you reproduce it). Include everything you think might be useful, the more information the better.

Improvements request and proposal

We and the community are continuously working to improve the firmware. Feel free to make an issue to request a new functionality.

Contributing code/Pull-Request

We welcome code contribution, this can be done by starting a pull-request.

If the change is big, typically if the change span to more than one file, consider starting an issue first to discuss the improvement. This will makes it much easier to make the change fit well into the firmware.

There is some basic requirement for us to merge a pull request:

  • Describe the change
  • Refer to any issues it effects
  • Separate one pull request per functionality: if you start writing "and" in the feature description consider if it could be separated in two pull requests.
  • The pull request must pass the automated test (see test section bellow)

In your code:

  • 2 spaces indentation
  • Make sure the coding style of your code follows the style of the file.

Run test

To run the tests please have a look at the unit test documentation.