# Maintenance bottlenecks in the compiler distribution

**URL:** <https://discuss.ocaml.org/t/maintenance-bottlenecks-in-the-compiler-distribution/11045>\
**Category:** Community\
**Tags:** compiler\
**Created:** [December 23, 2022, 7:57pm UTC](https://discuss.ocaml.org/t/maintenance-bottlenecks-in-the-compiler-distribution/11045 "2022-12-23T19:57:36Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![dbuenzli](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/dbuenzli/32/18_2.png) [@dbuenzli](https://discuss.ocaml.org/u/dbuenzli)\
**Post date:** [December 31, 2022, 2:37pm UTC](https://discuss.ocaml.org/t/maintenance-bottlenecks-in-the-compiler-distribution/11045/4 "2022-12-31T14:37:52Z")

</div>

> [@gasche](#):
>
> It is interesting that, at least in that discussion, there seems to be no emphasis on the idea that people that submit PRs should also contribute to review work.

The whole narration around “contributing”, “PR welcome!” in OSS completely eluded the fact that making a PR is only a tiny and the easiest fraction of the work needed to integrate suggestions from random people from the internet into a cohesive result.

Maybe one thing you could try to add is a kind of tit for tat statement in `CONTRIBUTING.md`. Something of the form (better said) we are happy to take you work, but integrating and maintaining it takes time and ressources, there is a social expectation that for any PR merged of yours you will make a full review of another PR.

---

_[View the full topic](https://discuss.ocaml.org/t/maintenance-bottlenecks-in-the-compiler-distribution/11045)._