Are you looking to help the OCaml ecosystem, but not sure where to start? This page should give you some ideas of where the community thinks work is needed.
It’s worth keeping in mind that making the ecosystem just a little more usable, especially at critical points, can have massive implications downstream.
- odoc (needs help, high priority): the new standard documentation tool for OCaml. Unfortunately, it still needs some love – check out the Issues. This is a great place to contribute since a little effort on the documentation front can go a long way.
- doc.ocaml.org (non-existent): We need to have a central site for documentation of all packages. Odoc already does a good job on package documentation generation. We would like the CI infrastructure to build docs for each package as it tests it.
Web and Networking
Elasticsearch (needs help): the defacto standard search solution. ocaml-elasticsearch is abandoned.
- LablGTK3 (needs help) - not yet feature
complete as GTK2 state, see
- OWL (needs help): OCaml’s equivalent to Numpy and Pytorch. Currently, the project doesn’t support GPUs, which hurts its adoption by machine learning professionals.
- Google Cloud Platform: no bindings.
- NATS/NATS Streaming: no bindings. Part of the Cloud Native Foundation and gaining increased adoption.
- Our current bots for the discord channel use node.js code which is fairly unreliable. For example, rss-bot - a bot for displaying rss feeds in discord - tends to run out of memory. We’d much prefer to have a Discord library in OCaml, and possibly a bot creation library. This may be a good starting point.