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.
- Diskuv Box:
Adding native Windows support requires getting rid of the usage of small bash utilities.
Diskuv Boxis a file utility working on replacing bash utilities with a cross-platform program so that OCaml can easily work on Windows.
- DKML Installer - OCaml: a setup.exe for OCaml on Windows
and other platforms later. Needs help to:
- (small) provide a speedy sha256sum (ex. delegate to PowerShell / bundle binary) to verify downloaded contents. Currently bytecode version is very slow.
- (small) increase the Vagrant virtual machine tests to support more scenarios. Recent scenario is an installation path with a space in it (common on Windows); need more scenarios like that automatically tested.
- (medium) create a graphical installer Windows users are more familiar with. Currently setup.exe is a self-extracting console installer, and it fails when there is a process (ex. OCaml language server) in use that it is trying to replace.
- (large) allow MSYS2 CLANG64’s clang to be used rather than just the Microsoft Visual Studio compiler (MSVC). CLANG64 is compatible with MSVC, doesn’t require Administrator rights nor reboots (much easier install), and DKML already supports MSYS2. It is a “large” task because a few external packages may need some patching to work with clang.
Web and Networking
Elasticsearch (needs help): the de facto 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, scipy and Pytorch/Tensorflow.