[pdimitar]

Hey, I don't actually know Clojure beyond basics and several intros showing the overall framework of the language, its paradigms and generic philosophy (I don't count that as knowing a language).

I'd love to help but as it is, the original article convinced me that I shouldn't. As a commercial project maintainer myself I am all too well familiar with how many things one can miss if he doesn't write everything down and constantly manage information -- that's why I have a huge private Trello board.

I am not gonna scorn fellow extremely busy devs. But I will point out that as language maintainers your responsibility is bigger than mine. You should do your best.

If I ever decide to become an active Clojure user I definitely won't be only criticizing. I'll do my best to help!

[pdimitar]

Since this is getting downvoted, let me clarify:

It's my opinion that I don't have to be a Clojure expert with 5 years of experience in order to be able to recognize patterns in the language implementation and the way the ecosystem is governed, and eventually deduct I wouldn't want to associate with them for the time being.