Andy - you're the perfect model of someone stepping up from the community and making the situation better for everyone. I'm sure I speak for a large population when I say, Thank You.
For sure, I'd love to see an updated ClojureDocs-like system, hooked up to the build process and integrated into clojure.org. (Including all of contrib and CLJS) Pairing that with ClojureWerkz-style pages for all the contrib libraries would be an enormous leap forward (I'd love for the authors of ClojureWerkz to share the outline of the process that works for them). It would be in those dedicated pages that external links could guide the reader to further material. Kovas, I *very* much agree with all your points and think they are well said. Stuart, can you elaborate a little what better triage looks like? What are the current issues you're facing and what would make the process better for you? The ER metaphor perhaps isn't the best :) What are other ways the community can help get changes pushed along better and integrated? How might we better adjust the process to prevent patched and screened changes from sitting around for long stretches of time? My concern with growing the documentation on the dev.clojure is that it takes a CA to contribute. I think we'd be better served as a community to open up documentation contributions to everyone. One possible solution is moving clojure.org or a subset (docs.clojure.org) to a github repo, as integrated Markdown pages. Thoughts? Concerns? 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
