On Thu, Jul 7, 2011 at 1:42 AM, nchubrich <nchubr...@gmail.com> wrote:
> ... > > * It also can do a better job of attracting and retaining core > contributors. I cited an example of someone who posted a patch to > make refs persistent. She ended up being ignored, and left for > Erlang. But Clojure needs people like her. > ... Just wanted to address one of your points here, as the patch submission process has been brought up before. For clojure 1.3, I actually found a small bug in the accompanying son library. I tried to submit a patch via a github pull request. But it turns out that's not the correct path to take. You have to sign a "Contributor's Agreement", then submit a patch to Jira. Discussing both the error and the patch process was all plainly laid out<http://groups.google.com/group/clojure/browse_thread/thread/58691da25896a608/d17ba8c265e95fcb?lnk=gst&q=ClassCastException+on+%27clojure.data.json%2Fprint-json%27#d17ba8c265e95fcb>in a friendly manner by members of the core team. So I haven't had the problem your friend experienced. If it has been a problem in the past, it seems to have improved at this point. HTH Tim -- 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
