Skip to content

NEW_HARDWARE_POLICY.md: Use Discord rather than email#11333

Open
sensei-hacker wants to merge 1 commit intomaintenance-9.xfrom
sensei-hacker-patch-6
Open

NEW_HARDWARE_POLICY.md: Use Discord rather than email#11333
sensei-hacker wants to merge 1 commit intomaintenance-9.xfrom
sensei-hacker-patch-6

Conversation

@sensei-hacker
Copy link
Member

@sensei-hacker sensei-hacker commented Feb 15, 2026

User description

Updated contact method for hardware feature requests.


PR Type

Documentation


Description

  • Updates hardware feature request contact method from email to Discord

  • Directs users to Discord server for initial developer team communication

  • Maintains email for hardware specifications delivery arrangement


Diagram Walkthrough

flowchart LR
  A["Feature Request"] -- "Contact via" --> B["Discord"]
  B -- "Arrange delivery via" --> C["Email"]
Loading

File Walkthrough

Relevant files
Documentation
NEW_HARDWARE_POLICY.md
Replace email with Discord for hardware requests                 

docs/policies/NEW_HARDWARE_POLICY.md

  • Changed primary contact method from email to Discord for hardware
    feature requests
  • Updated link to point to Discord server instead of email address
  • Kept email as secondary communication channel for hardware
    specifications delivery
+1/-1     

Updated contact method for hardware feature requests.
@qodo-code-review
Copy link
Contributor

ⓘ You are approaching your monthly quota for Qodo. Upgrade your plan

PR Compliance Guide 🔍

All compliance sections have been disabled in the configurations.

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.
2. After opening a feature request, Requester is advised to contact the core development team via [Discord](https://discord.gg/peg2hhbYwN) mentioning the open feature request and communicate with developer team via email to arrange hardware and specifications delivery.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: Ensure the provided Discord invite link is permanent to prevent it from expiring, possibly by using a server vanity URL if available. [general, importance: 6]

Suggested change
2. After opening a feature request, Requester is advised to contact the core development team via [Discord](https://discord.gg/peg2hhbYwN) mentioning the open feature request and communicate with developer team via email to arrange hardware and specifications delivery.
+2. After opening a feature request, Requester is advised to contact the core development team via [Discord](https://discord.gg/permanent-invite-link) mentioning the open feature request and communicate with developer team via email to arrange hardware and specifications delivery.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant