> Hi all, > > Now that I have my shiny new, clojure-dev membership, I'd like to pitch in. > I took a look at the pages describing how to contribute. > > http://clojure.org/contributing > http://clojure.org/patches > > The process for contributing is pretty clear, but I'm finding it hard to find > anything appropriate to my skill level and familiarity with the Clojure / > clojure-contrib source to work on. Even finding an appropriate issue from a > 'process' perspective is difficult, e.g. I ran a JIRA search on open, > unassigned, issues and found that many of them already had patches associated > with them, were waiting for someone do something or had comments that seemed > to imply that someone was already working on the issue or perhaps was no > longer even an issue. To say nothing of the difference between an issue > being assigned to backlog, approved backlog, and the various releases. > > I'm wondering if anyone has some suggestions on tasks that might be useful > for a newbie to work on -- documentation or grunt programming tasks would be > fine. Maybe updating or expanding test cases?
Hi Rett, Contributing a 1.3-ready Alioth benchmark to https://github.com/clojure/test.benchmark would be terrific. These act as test cases for both functionality and performance. Improving the docs at http://dev.clojure.org/ is also a great help (although the site seems down atm). Cheers, Stu Stuart Halloway Clojure/core http://clojure.com -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
