# Wanted: new maintainer for cppo

**URL:** <https://discuss.ocaml.org/t/wanted-new-maintainer-for-cppo/2959>\
**Category:** Community\
**Created:** [November 27, 2018, 3:05am UTC](https://discuss.ocaml.org/t/wanted-new-maintainer-for-cppo/2959 "2018-11-27T03:05:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mjambon](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/mjambon/32/6180_2.png) [@mjambon](https://discuss.ocaml.org/u/mjambon)\
**Post date:** [November 27, 2018, 3:05am UTC](https://discuss.ocaml.org/t/wanted-new-maintainer-for-cppo/2959/1 "2018-11-27T03:05:13Z")

</div>

[Cppo](https://github.com/ocaml-community/cppo) is a C-style preprocessor for OCaml. I started the project in 2009, when I was working on yojson and didn’t want to be tied to camlp4 for simple things like `#include` and conditional compilation. Since then, other projects have used it, typically as a last resort to manage version incompatibilities. Today, 57 packages in opam depend directly on cppo.

The project was recently handed off to [ocaml-community](https://github.com/ocaml-community/meta) in an effort to benefit from a wider community. I no longer wish to be in charge of supervising the project because it’s too much for me, when combined with other projects. Ideally, we’re looking for a person maintaining cppo with the support of their employer. The project is very stable. There are no new features in sight and very few bug reports. Maintenance would consist in roughly one day a month, generally spent answering incoming questions and working with users to solve their problems or review patches.

Let us know if you’re interested!

Best,

Martin

---

<div class="post-metadata">

**Author:** ![perry](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/perry/32/518_2.png) [@perry](https://discuss.ocaml.org/u/perry)\
**Post date:** [November 27, 2018, 2:02pm UTC](https://discuss.ocaml.org/t/wanted-new-maintainer-for-cppo/2959/2 "2018-11-27T14:02:13Z")

</div>

Given the relatively light load, if you can’t find a new single individual to maintain it, several of us could probably take responsibility for integrating pull requests and making sure that it continues to build with new OCaml releases, which is the main responsibility.

---

<div class="post-metadata">

**Author:** ![gasche](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/gasche/32/4_2.png) [@gasche](https://discuss.ocaml.org/u/gasche)\
**Post date:** [December 1, 2018, 10:15am UTC](https://discuss.ocaml.org/t/wanted-new-maintainer-for-cppo/2959/3 "2018-12-01T10:15:28Z")

</div>

I think that it would make sense to have someone from the Dune team looking at it, because version-conditional logic and configuration logic interact with the build system.