Make project more inviting for developers

[abooij]

What is needed to make this project more developer-friendly?

[xavier83]

I have no experience in display servers but interested in contributing, what can i do to help?

[abooij]

Basically all the things that I think need attention are recorded as issues.

If you want to avoid having to dive into wayland documentation for a few weeks before you can get started, then I think #1, #2 and #6 are the most important issues right now.

#1 is an issue that a number of Haskell projects are suffering from, and likely requires work on cabal. So what I'd really like at this stage is a decent workaround (some kind of Makefile? autotools? but how do these interact with cabal?).

I'm not sure how to do #2 yet and personally don't consider it top priority: "simply" having a drop-in replacement of the wayland library will attract more attention than some arcane new library in a language that only a fraction of programmers know how to use.

#6: this shouldn't be too difficult (although there is quite some work involved). It would be nice if our drop-in replacement of libwayland were able to match the speed of libwayland. I don't think anyone is really benchmarking libwayland at the moment, but when they do, we should not come out an order of magnitude slower. In essence the binary (de)serialization code is already there; it just needs converting to use a different library.