Skip to content

Commit

Permalink
Merge branch 'development' into de_fpv_cam_mix
Browse files Browse the repository at this point in the history
  • Loading branch information
digitalentity committed Dec 22, 2018
2 parents a1b9440 + 38c0caa commit 9936d53
Show file tree
Hide file tree
Showing 3,710 changed files with 204,583 additions and 2,496,196 deletions.
The diff you're trying to view is too large. We only load the first 3000 changed files.
25 changes: 0 additions & 25 deletions .github/ISSUE_TEMPLATE.md

This file was deleted.

32 changes: 32 additions & 0 deletions .github/ISSUE_TEMPLATE/Bug_report.md
@@ -0,0 +1,32 @@
---
name: "\U0001F41B Bug report"
about: Report an issue to help make INAV better

---

## Current Behavior
<!-- If applicable, add screenshots, videos and blackbox logs to help explain your problem. -->

## Steps to Reproduce
<!-- Steps to reproduce the behavior: -->
1.
2.
3.
4.

## Expected behavior
<!-- A clear and concise description of what you expected to happen. -->

## Suggested solution(s)
<!-- How could we solve this issue? What changes would need to made to INAV? -->

## Additional context
<!-- Add any other context about the problem here. -->
<!-- Go to CLI, execute `dump` command copy its output to [PasteBin](https://pastebin.com) and provide a link to a paste here -->

---
<!-- PLEASE FILL THIS OUT -->
<!-- Use CLI 'version' command to get version string -->

- FC Board name and vendor:
- INAV version string:
21 changes: 21 additions & 0 deletions .github/ISSUE_TEMPLATE/Feature_request.md
@@ -0,0 +1,21 @@
---
name: "\U0001F680Feature request"
about: Suggest a new feature for INAV

---

## Current Behavior
<!-- A clear and concise description of what is the current behavior / usecase. -->

## Desired Behavior
<!-- A clear and concise description of what you want to happen. -->

## Suggested Solution
<!-- Suggest a solution that the community/maintainers/you may take to enable the desired behavior -->
<!-- NOTE: Feature Requests without suggested solutions may not be addressed with the same level of urgency as those that have suggested solutions -->

## Who does this impact? Who is this for?
<!-- Who is this for? All users? Airplane users? Beginners? Advanced? Yourself? People using X, Y, Z, etc.? -->

## Additional context
<!-- Add any other context or links about the feature request here. -->
18 changes: 18 additions & 0 deletions .github/ISSUE_TEMPLATE/Question.md
@@ -0,0 +1,18 @@
---
name: "\U00002753Question"
about: Have a question?

---

For immediate help, just ask your question on one of the following platforms:

* [Telegram channel](https://t.me/INAVFlight)
* [Facebook group](https://www.facebook.com/groups/INAVOfficial)
* [RC Groups thread](https://www.rcgroups.com/forums/showthread.php?2495732-Cleanflight-iNav-%28navigation-rewrite%29-project)

You can also read public documentations or watch video tutorials:

* [Official documentation](https://github.com/iNavFlight/inav/tree/master/docs)
* [Official Wiki](https://github.com/iNavFlight/inav/wiki)
* [Video series by Painless360](https://www.youtube.com/playlist?list=PLYsWjANuAm4qdXEGFSeUhOZ10-H8YTSnH)
* [Video series by Paweł Spychalski](https://www.youtube.com/playlist?list=PLOUQ8o2_nCLloACrA6f1_daCjhqY2x0fB)
58 changes: 58 additions & 0 deletions .github/stale.yml
@@ -0,0 +1,58 @@
# Configuration for probot-stale - https://github.com/probot/stale

# Number of days of inactivity before an Issue or Pull Request becomes stale
daysUntilStale: 60

# Number of days of inactivity before a stale Issue or Pull Request is closed.
# Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
daysUntilClose: 14

# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
exemptLabels:
- BUG
- Feature Request
- Pinned

# Set to true to ignore issues in a project (defaults to false)
exemptProjects: false

# Set to true to ignore issues in a milestone (defaults to false)
exemptMilestones: true

# Label to use when marking as stale
staleLabel: Inactive

# Comment to post when marking as stale. Set to `false` to disable
markComment: >
This issue / pull request has been automatically marked as stale because it
has not had any activity in 60 days. The resources of the INAV team are limited,
and so we are asking for your help.
This issue / pull request will be closed if no further activity occurs within two weeks.
# Comment to post when removing the stale label.
# unmarkComment: >
# Your comment here.

# Comment to post when closing a stale Issue or Pull Request.
closeComment: >
Automatically closing as inactive.
# Limit the number of actions per hour, from 1-30. Default is 30
limitPerRun: 30

# Limit to only `issues` or `pulls`
# only: issues

# Optionally, specify configuration settings that are specific to just 'issues' or 'pulls':
# pulls:
# daysUntilStale: 30
# markComment: >
# This pull request has been automatically marked as stale because it has not had
# recent activity. It will be closed if no further activity occurs. Thank you
# for your contributions.

# issues:
# exemptLabels:
# - confirmed
2 changes: 0 additions & 2 deletions .gitignore
Expand Up @@ -20,6 +20,4 @@ docs/Manual.pdf
README.pdf

# build generated files
/src/main/fc/settings_generated.h
/src/main/fc/settings_generated.c
/settings.json
4 changes: 2 additions & 2 deletions .travis.yml
Expand Up @@ -28,7 +28,7 @@ before_install:

install:
- ./install-toolchain.sh
- export TOOLCHAINPATH=$PWD/gcc-arm-none-eabi-6-2017-q2-update/bin
- export TOOLCHAINPATH=$PWD/gcc-arm-none-eabi-7-2018-q2-update/bin
- export PATH=$TOOLCHAINPATH:$PATH

before_script:
Expand All @@ -41,7 +41,7 @@ script: ./.travis.sh
cache:
apt: true
directories:
- $PWD/gcc-arm-none-eabi-6-2017-q2-update
- $PWD/gcc-arm-none-eabi-7-2018-q2-update

notifications:
#slack: inavflight:UWRoWFJ4cbbpHXT8HJJlAPXa
Expand Down
91 changes: 91 additions & 0 deletions AUTHORS
@@ -0,0 +1,91 @@
This is at least a partial credits-file of people that have contributed to the INAV project.
If you believe you should be on this list - feel free to open a PR updating it. For faster
inclusion into this list please provide information about which part of code belongs to you.

Albert Kravcov
Alberto García Hierro
Alex Gorbatchev
Alex Zaitsev
Alexander Fedorov
Alexey Stankevich
Andre Bernet
Andreas Tacke
Andrew Payne
Austin St. Aubin
Bas Huisman
Ben Hitchcock
Boris B
Brnadon Miller
ChiggerPepi
Chris Campbell
Chris Mavrakis
Chris Nisbet
Chris Penny
Damjan Adamic
Dave Pitman
David Bieber
Davide Bertola
Denis Kisselev
Dominic Clifton
Frank Zhao
Fredrik Steen
Gareth Wilkins
Gaël James
Gregor Ottmann
Google LLC
Hyon Lim
James Harrison
Jan Staal
Jeremy Waters
Joe Poser
Joel Fuster
Johannes Kasberger
Jonas Harnesk
Jonathan Hudson
Joshua Bardwell
Juan González
Kemal Hadimli
Kieran Moore
Konstantin Sharlaimov
Krzysztof Rosinski
Kyle Manna
Larry Davis
Marc Egli
Mark Williams
Martin Budden
Matthew Evans
Mauro Mombelli
Max Winterstein
Michael Corcoran
Michael Hope
Michael Jakob
Michel Pastor
Miha Valencic
Mikael Blomqvist
Moritz Ulrich
Moshen Chan
Nathan Tsoi
Nicholas Sherlock
Paul Fertser
Paul Rogalinski
Pawel Spychalski
Petr Ledvina
Phillip Jones
Pierre Hugo
Richard Birkby
Richard Lehey
Richard Marko
Rimas Avizienis
Sam Cook
Sami Korhonen
Samuel Brucksch
Scott Shawcroft
Sean Vig
Stefan Grufman
Stefan Haubold
Steve Amor
Thomas Buck
Tim Eckel
Trey Marc
Tuomas Kuosmanen
Zap Andersson
46 changes: 46 additions & 0 deletions CODE_OF_CONDUCT.md
@@ -0,0 +1,46 @@
# Contributor Covenant Code of Conduct

## Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

## Our Standards

Examples of behavior that contributes to creating a positive environment include:

* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

* The use of sexualized language or imagery and unwelcome sexual attention or advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a professional setting

## Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

## Scope

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]

[homepage]: http://contributor-covenant.org
[version]: http://contributor-covenant.org/version/1/4/

0 comments on commit 9936d53

Please sign in to comment.