I’m currently maintaining a couple of (numerical) libraries, mostly Fortran or at least with Fortran bindings, and Fortran related tooling on conda-forge and are looking for co-maintainers. While I try to involve the upstream maintainers with the packaging where possible, there are still several packages only maintained by myself:
- eigenexa (C++, MPI, make)
- elpa (Fortran, C, Cuda, MPI, autoconf)
- elsi (Fortran, MPI, cmake)
- findent (C++, autoconf)
- ford (Python)
- fprettify (Python)
- iso_varying_string (Fortran, cmake)
- libnegf (Fortran, MPI, cmake)
- libomm (Fortran, MPI, autotools)
- matrixswitch (Fortran, MPI, autotools)
- pexsi (C++, MPI, cmake)
- plplot (Fortran, C, C++, Tcl, cmake)
- superlu_dist (C++, MPI, cmake)
The difficulty of maintaining those packages varies greatly, usually the CMake ones are quite straight-forward, autoconf ones are almost always a real pain (only plain make is worse) and most of the time require a lot of patching. Also, more languages usually mean more potential trouble.
Maintaining on conda-forge is mostly automated by bots (if the package is hosted on GitHub or GitLab), but occasionally you need to debug a broken build. Some packages are hosted elsewhere (SourceForge, custom GitLab, Bitbucket, …) and updates are not automatically found. There is a great community around conda-forge, very detailed documentation and of course co-maintainers who can help you in case of questions.
If you are interested in helping out with any of the packages listed here, let me know.