OpenCV 3.1 Haskell binding

haskell-opencv is an in-development opensource Haskell binding to the popular OpenCV-3.1 C++ Computer Vision library. Note that other Haskell OpenCV bindings already exist but these target the older 2.4 version of OpenCV.

The library comes with haddock documentation. Example programs are embedded in the documentation and are automatically build and run as part of the test-suite. They output images which are referenced from the documentation. Besides documentation the library also comes with a test-suite and the beginning of a benchmark suite. Finally, the library is already being used in production by LumiGuide for detecting available space to park your bicycle or car in big parking facilities.

The library is not finished yet. A lot of functions still need to be bound. However, the basis is there to easily bind missing functionality. All the core pieces are in place: core datatypes like points, sizes, polygons and most importantly matrices are there. It's also easy to bind missing datatypes. We use inline-c to inline C++ code in our Haskell code. We also have a way of dealing with exceptions originating from C++ code.

The goal of this MuniHac project is simply to bind more functionality. Roel and Bas will be available as mentors and can help you get started quickly and provide advice on how to best represent OpenCV functions in Haskell.

Servant

Servant-python

Required skill level: Intermediate

Servant comes with a library `servant-foreign` that allows us to generate http clients in different languages like javascript and ruby. A servant-python library has been requested a few times, and it would be nice to add this to servant.

You could look at the code in `servant-js` and adapt it to generate python code. Preferably using the python `requests` library.

ghc-mod – Haskell editor integration for Emacs, Vim, Atom etc.

ghc-mod-core: aka. "ghc-mod The Good Parts"

ghc-mod's codebase has been accumulating a lot of functionality over the years,
leading to a significant maintenance burden in keeping everything working. We're
trying to split the essential parts off into a new library and eventually rebase
everything else on top of that.

ghc-mod: make using different compiler versions across projects easier

One of the major problems with ghc-mod is the fact that we directly link against
the GHC API library which essentially means we can only support one GHC version
per ghc-mod installation. Since ghc-mod now supports Stack this has become a
much larger problem since GHC version changes are now transparent to users.

There are two approaches to solving this that we're considering: Either we
(re)compile the ghc-mod executable at runtime against the GHC version we detect
the project to be using or we use some dynamic linker voodoo. I've been
prototyping a way to do the latter (see rts-loader package on Hackage) but it's
not clear yet if this is a good idea or not.