Month after month there are more and more people who announce their open source Clojure projects. This is great and we can't get enough of this.
What is not great is how easy it often is to get started with some of the projects. Some of the most basic "maintainer best practices" are completely ignored, even though it often takes 3 minutes to fix some annoyances. So I wrote a little ranty blog post about what you can do to make your project awesome (or at least not suck). This also sums up what we've been trying to practice with ClojureWerkz. I hope it will help the Clojure community to be better library maintainers. Here it is: http://blog.clojurewerkz.org/blog/2013/04/20/how-to-make-your-open-source-project-really-awesome/ Now you have no excuse to not make your library totally awesome. -- MK http://github.com/michaelklishin http://twitter.com/michaelklishin -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
