I look at it from the psychological point of view. There is a similar design decision in a website world - mandatory login vs relaxed login. For years a lot of webmasters were quite inert to even look at possibility to relax login requirement for core site activities.
However in the online shopping field which is very competitive webmasters realized that for example adding products to the cart without login gives better conversion rates. We don't need to sign anything to answer on StackOverflow, even login is not required now. We don't need to sign anything to make "GitHub pull requests" to a lot of projects. Somehow it makes life smoother. I don't know what impact of this barrier can be for Clojure. I realize it can be quite negligible. However as example I have not signed some papers for my Google Closure library patch in the past. It just looked so absurd to fill some papers for "if (!variable)" => "if (variable === 0)" kind of fix. I realize that there are real world constraints and the world is not perfect and the world is not even close to be perfect. But dreaming about better ways is a part of Clojure community, isn't it? May be the best solution is just to be vocal that the sign process is quick and easy now. Or may be doing nothing about it because there are more priority tasks. I hope I convey my perspective better now. P.S. Please don't "cut my air away" :)) -- 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/d/optout.
