I have listed some projects here
that I think have decent prospects.
I also did this talk
about how we collaborate in this community. I very strongly recommend watching it if you are serious about working with core folks!
One thing that is important for core contributors is that they have a shared understanding about where Elm is headed and how we plan to get there. So on that note, the ideas you suggested make me worried about how different our perspectives are at this moment in time. E.g. There are no plans to add user-definable type classes to Elm, so there is no work to do there. (It has been discussed endlessly, so def this isn't the thread to go down that road.) Making Elm on servers is not just about making a new backend as I detail here
. Some theorize that SML was actually hurt by having lots of proofs about the language because it ended up being a barrier to change.
Point is, I think you are trying to do (idea from academia => Elm) whereas we try to focus more on (problem from day-to-day work => research-informed engineering). Here are examples of how each of these might go:
- "I spent a year or two learning Coq" => "let's find something to do with that"
- "man, I really think that step-by-step debuggers are annoying" => "how could we use the fact that Elm is pure to do better?"
As a general rule, we try to do the 2nd one.
Anyway, hope the links are helpful! Hope the context about design process is helpful too! (I think it may sound harsh, but it's more that I have a meeting in a few minutes and cannot edit more!)