# 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:** 57

<div class="post-metadata">

**Author:** ![ToucheSir](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/touchesir/32/14411_2.png) [@ToucheSir](https://discourse.julialang.org/u/ToucheSir)\
**Post date:** [August 16, 2023, 5:44pm UTC](https://discourse.julialang.org/t/making-the-review-process-more-pleasant-for-new-contributors/102604/57 "2023-08-16T17:44:25Z")

</div>

[Where should Julia feature requests go? - #19 by mbauman](https://discourse.julialang.org/t/where-should-julia-feature-requests-go/102835/19) has a great summary of how other big and successful projects in this space manage their issues. Is anyone aware of a similar analysis for PRs/code changes? It would be nice to borrow from an approach that we already know works and run trials/quick experiments to get the ball rolling.

---

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