Stuart: Regarding making clojure.test/clojure.string/etc. contrib libraries, does it make sense to also move clojure.core to a "contrib" style library. The idea here would be that "Clojure 1.6" is the bundling of all smaller Clojure lib/contrib subsets, whose version number is always in sync with core. Developers could always grab just the core still. This might also ease some pains for producing and releasing conditional compilations of core (for example, for portable devices). This offsets the breaking change moving forward (the bundle is a migration path) and might make for a better user/developer experience. The new tradeoff is Clojure is now a bundled release, increasing the size of the jar.
Regarding triage, would it help if blocking defects were alerted on the weekly emails that Andy sends out? Would you prefer this to be a separate email? I also think some education (a better contributors guide maybe) could help fix some of the other issues you mentioned. To Rich / Stuart / Maintainers of clojure.org - what would have to be in place to make a git-managed, Markdown-based, community-driven documentation site (doc.clojure.org) happen? Ideally this site would also be hooked into a ClojureDocs system (either through an iframe or moving ClojureDocs over to the new project). Would it be possible to handle these documentation contributions outside of the CA, licensing everything some CC license? I also agree with Kovas, even small changes/updates could help the newcomers experience a lot. Thanks everyone for the great discussion so far! There are a lot of great ideas being teased out here. Paul -- 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
