# Making the review process more pleasant for new contributors

**URL:** <https://discourse.julialang.org/t/making-the-review-process-more-pleasant-for-new-contributors/102604>\
**Category:** General Usage\
**Tags:** github, contributing\
**Created:** [August 8, 2023, 2:00pm UTC](https://discourse.julialang.org/t/making-the-review-process-more-pleasant-for-new-contributors/102604 "2023-08-08T14:00:25Z")\
**Posts on this page:** 1\
**Showing post:** 24

<div class="post-metadata">

**Author:** ![adienes](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/adienes/32/37459_2.png) [@adienes](https://discourse.julialang.org/u/adienes)\
**Post date:** [August 8, 2023, 9:22pm UTC](https://discourse.julialang.org/t/making-the-review-process-more-pleasant-for-new-contributors/102604/24 "2023-08-08T21:22:24Z")

</div>

GitHub has lots of features that could possibly be useful (or possibly just noise?)

for example, consider the following policy:

- anyone who has authored a commit can “approve” PRs (just an endorsement, not actually making it ready to merge)
- PRs getting some X number of unanimous approvals from community contributors are labeled with “needs maintainer review” or something like that

---

_[View the full topic](https://discourse.julialang.org/t/making-the-review-process-more-pleasant-for-new-contributors/102604)._