# Please slow down the code review process!

**URL:** https://discourse.itk.org/t/please-slow-down-the-code-review-process/631
**Category:** Community
**Created:** [January 30, 2018, 12:50pm UTC](https://discourse.itk.org/t/please-slow-down-the-code-review-process/631 "2018-01-30T12:50:53Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![jhlegarreta](https://discourse.itk.org/user_avatar/discourse.itk.org/jhlegarreta/32/476_2.png) [@jhlegarreta](https://discourse.itk.org/u/jhlegarreta)
#### Post date: [January 31, 2018, 4:22pm UTC](https://discourse.itk.org/t/please-slow-down-the-code-review-process/631/8 "2018-01-31T16:22:20Z")

</div>

Having some policy that we agree upon may be sensible.

Some suggestions, such as relying on the type of topic/patch, are interesting to accommodate the process.

Having a deadline or “slow down” button, requiring the approval of some maintainers, or a number of people, etc. seem desirable also.

But implementing these in `GitHub` (remember that [ITK is transitioning to GitHub](https://discourse.itk.org/t/gearing-up-for-itk5/515)) or requiring the `GitHub` people do it may not be easy/out of reach.

Having said that, the truth is that:

- Current **maintainers are mostly based in the US** , and accommodating different time zones may not be that easy, and workdays may also differ across countries, across companies, etc.

- We should acknowledge that maintainers’ institutions may also have **other constraints** (funding agencies, etc.) that one, including me, as a community member, may be unaware of.

- People having push access are trustworthy and work to the best of their possibilities, including outside work hours, to make **ITK better for the community** 👌, and the funding agencies, institutions, scientific community. Even if this means merging within short delays.

- A good feature, module, class or awesome contribution in terms of bug fixes can beat missing a review. **So there is always a chance to improve ITK**!!

Just a short explanation @Niels_Dekker: the `gerrit` review system **automatically** adds people as reviewers when it detects that a given user made some commit on the file at issue at some point in history.

---

_[View the full topic](https://discourse.itk.org/t/please-slow-down-the-code-review-process/631)._