On Mon, 2011-07-25 at 09:59 -0700, nchurch wrote: > +1 to writing an etiquette document.
In place of an etiquette document I suggest the book called "Producing Open Source Software". In this generally useful book there is some advice, mostly directed at project leads but this section is relevant: http://producingoss.com/en/producingoss.html#communications I don't think the original poster intended to troll but the post certainly fell under the rubric of "kibitzing" (def: "A Kibitzer is a non-participant who hangs around offering (often unwanted) advice or commentary"). The advice was "unwanted" as the issue was already addressed in the video. Based on the book, I think Rich is doing an excellent job, especially in the area of communication. Tim Daly -- 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