Seeking Clarification, Multiple Opinions, and Reminding Reviewers

Sometimes however, they can also get a bit carried away and become too perfectionistic. If you feel some of the requests are unreasonable, out of scope, or merely a matter of personal preference, try to nicely remind the reviewers that you may not intend this code to be 100% perfect or that you have different taste in some regards and press them on whether they think that these requests are *critical* to the PR's success. While we do have a set of [official standards for the Nix community](https://github.com/NixOS/rfcs/), we don't have standards for everything and there are often multiple valid ways to achieve the same goal. Unless there are standards forbidding the patterns used in your code or there are serious technical, maintainability or readability issues with your code, you can insist to keep the code the way you made it and disregard the requests. Please communicate this clearly though; a simple "I prefer it this way and see no major issue with it" can save you a lot of arguing. If you are unsure about some change requests, please ask reviewers *why* they requested them. This will usually reveal how important they deem it to be and will help educate you about standards, best practices, unwritten rules aswell as preferences people have and why. Some committers may have stronger opinions on some things and therefore (understandably) may not want to merge your PR if you don't follow their requests. It is totally fine to get yourself a second or third opinion in such a case. ### Committers work on a push-basis It's possible for you to get a review but nothing happens afterwards, even if you reply to review comments. A committer not following up on your PR does not necessarily mean they're disinterested or unresponsive, they may have simply forgotten to follow up on it or had some other circumstances preventing them from doing so. Committers typically handle many other PRs besides yours and it is not realistic for them to keep up with all of them to a degree where they could reasonably remember to follow up on all PRs that they had intended following up upon. If someone left an approving review on your PR and didn't merge a few days later, the most likely case is that they simply forgot. Please see it as your responsibility to actively remind reviewers of your open PRs.

This section advises asking reviewers for the rationale behind change requests to understand their importance and learn about standards. It acknowledges that some committers may have strong preferences, and suggests seeking additional opinions if needed. Furthermore, it emphasizes that committers may forget to follow up on PRs, even after approving reviews, and encourages users to actively remind them to ensure the PR is not overlooked.