# PRs in distress

**URL:** https://discourse.nixos.org/t/prs-in-distress/3604
**Category:** Development
**Created:** [August 3, 2019, 1:31am UTC](https://discourse.nixos.org/t/prs-in-distress/3604 "2019-08-03T01:31:08Z")
**Posts on this page:** 1
**Showing post:** 67

<div class="post-metadata">

### Author: ![doronbehar](https://discourse.nixos.org/user_avatar/discourse.nixos.org/doronbehar/32/1387_2.png) [@doronbehar](https://discourse.nixos.org/u/doronbehar)
#### Post date: [August 19, 2023, 10:28am UTC](https://discourse.nixos.org/t/prs-in-distress/3604/67 "2023-08-19T10:28:05Z")

</div>

> [@errnoh](#):
>
> What’s the protocol on PRs for software that requires specific hardware and/or setup?

Unfortunately, we don’t have such a policy, very similarly to how we lack even more basic policies (people are complaining about that these days in [this thread](https://discourse.nixos.org/t/where-did-you-get-stuck-in-the-nix-ecosystem-tell-me-your-story/31415/)). However, in my experience, if 1 person is able to verify the change is working with the hardware, or even if none, and the changes look good and software at least compiles and is able to not crash for a `--help` argument, it should be good to go.

For the 1st PR you linked, getting a 👍 from that person who requested the feature would greatly benefit, after most of the review is done.

---

_[View the full topic](https://discourse.nixos.org/t/prs-in-distress/3604)._