One of the things that occurred to me at last night's Meetup is that there seems to be a sizable group of people who are keen on contributing to Clojure, including basic "drudge" work. It also seems apparent that having a decent test suite is valuable (if only for the sake of appearances and adoption), though I tend to agree that it's not a good use of Rich's time.
While this contribution would indeed be easier with git, I'm disinclined to wait: I'm personally intending to take a look at the existing tests in contrib, and if I can figure out the test framework, I'll crank out a few tests for the core. If a few people did this, tests will accrue over time. Perhaps more importantly, if we manage to inculcate the attitude that questions, bugs, and misunderstandings should be captured as tests, then the important areas — edge cases and bug fixes — will grow coverage, all without Rich wasting his time. Thoughts? Opinions? Advice on the test framework? Would my time be better spent documenting what I learn about the test framework? Should I go back to bed and get more sleep? :) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
