All that said, the structure of the code definitely does help a lot in lowering the bar for contributions. When Don Stewart was on the Haskell Cast [1], he mentioned that the way they use Haskell allows contributions from people who not only have no prior functional experience but who have little CS background at all past basic programming literacy. Much of the ability to do this comes from Haskell's rigorous isolation of side effects.
[1]: http://www.haskellcast.com/episode/002-don-stewart-on-real-w... around 42:40 or so
When I finally got around to learning Haskell, I found myself able to productively make small changes within a few days. A lot of the more... idiomatic? uses of Functor and Applicative took another week or so to learn. The books Learn You a Haskell and Real World Haskell were helpful there.
I am by no means an expert at Haskell now, but within a few weeks I was able to contribute to most areas of the stack.
This is very true in every language, and doubly so in Haskell. If you just take the language as it is without any context, the language leaves whole classes of problems with a ridiculous overabundance of potentially viable solutions.
The one that springs to mind most prominently is error handling. What's the right way to do this? Option types? Exceptions? EitherT? We even explored a library that used type classes to provide Java-style checked exceptions.
We sorted this out early, when the "team" was just 2 people working in extra hours, but if we'd still been in that state when we scaled up, the project would have been a disaster.
FYI, the solution we came up with was to use option types for all recoverable errors. We only use exceptions for nonrecoverable failures that should trigger production alerts.
I was surprised how fast people were picking up the language when I started
It is way different learning the language surrounded by teachers and a working environment. That was my takeaway.
I can code in the language no problem but sometimes I feel that idiomatic ideal is always just out of reach to all but the Simons.
Is this a feature of the way your code is structured that simplifies what people have to understand about the language before they can contribute?