Skip to content

[pull] master from iNavFlight:master #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pull merged 2 commits into from
May 31, 2025
Merged

[pull] master from iNavFlight:master #21

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5e325a8
NEW_HARDWARE_POLICY.md: link to hardware design guidelines
sensei-hacker May 31, 2025
498526b
Update NEW_HARDWARE_POLICY.md
sensei-hacker May 31, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/policies/NEW_HARDWARE_POLICY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,3 +68,8 @@ If one of the core developers has the hardware in possession they may opt in and
1. Requester is advised to open a feature request to add support for certain hardware to INAV by following [this link](https://github.com/iNavFlight/inav/issues/new/choose)

2. After opening a feature request, Requester is advised to contact the core development team by [email](mailto:coredev@inavflight.com) mentioning the open feature request and communicate with developer team via email to arrange hardware and specifications delivery.


## See also
[Hardware Design Guidelines](https://github.com/iNavFlight/inav/wiki/Hardware-Design-Guidelines)