Good point. I remember a SproutCore (JS framework) documentation project[1] in which one of the developers would teach a course to some selected people, and in exchange they would write a manual for the framework. In the end they didn't reach the sponsorship quota and the thing was cancelled.
[1] http://erichocean.com/book/index.html On Wednesday, September 5, 2012 8:02:20 PM UTC-3, Brian Marick wrote: > > > On Sep 5, 2012, at 12:15 PM, Simone Mosciatti wrote: > > > I would say raise money to help people improve their project > (documentation is a very important part that). > > Many people who are good at writing code are not good at writing > documentation. Writing good explanations is hard, even if you have a knack > for it. It's not something J. Random Superprogrammer can just automatically > do by virtue of his enormous brain. > > If money is to be spent, it would be better spent on people other than the > developers, people who *don't* know the project (because the troubles they > have learning it will inform their documentation), are quick studies, and > are skilled explainers. > > ----- > Brian Marick, Artisanal Labrador > Contract programming in Ruby and Clojure > Occasional consulting on Agile > Writing /Functional Programming for the Object-Oriented Programmer/: > https://leanpub.com/fp-oo > > > -- 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
