> If I was thinking of contributing to Clojure, this post is reason enough to stay away from it. Without wanting to sound flippant or rude, I think they'd be c

> If I was thinking of contributing to Clojure, this post is reason enough to stay away from it. Without wanting to sound flippant or rude, I think they'd be cool with that. They're talking about contributions to the core language here. Not fixing typos in a README. In mature projects like this, all the low-hanging fruit is done. You can't just take a notion some weekend and fire off a useful pull request. It requires an investment. To make a good contribution to Clojure you have to.... - clearly define the problem that needs to be solved - get other people on the core team to agree that it needs to be solved - document a number of ways to solve it, discuss with the community which one will work best - let these ideas stew for a while, people might change their minds The above constitutes 95% of the work and would typically take months rather than days. Once all that's done, coding up the implementation is the easy bit.