Gang, Reading the Gradle Userguide PDF offline while being on the ride [2] it stuck to me: I felt very comfy & home when knowing there is a PDF on my disk that covers all i need for a OSS tool to work start with.
This is the same thing that Sonatype does with their Maven books for example. Also Hudson took that approach: [1] I think that would also be a good thing for the main OPS4J Projects. Sure, its a huge amount of work, but i think that really needs to be done for the Projects that we call almost "Product" status (in the OPS4J wiki there is also the distinction of Projects possibly raising up to Products when they mature). Not poking on the projects vs. product distinction here.. just maybe some projects need that step to benefit the user. On some other mailinglists (for example Apache Aries, who employs some Pax tools in their toolchain) sometimes i read about Pax Tools are not well documented. I think its not necesary true in all cases, but there is a reason for people telling that on a mailing list. So, what i would like to ask: - Which projects do you think need major, book-reference like documentation ? - What do you recommended as a technical solution. Ultimatively i would like to have that in Html (online+offline) + PDF ? Also it needs to be strongly versioned. Not sure, possibly it makes sense to put that all in one "Pax" book. But the tooling stuff and Pax Web (a service) are quite different things. WDYT? Toni [1] http://www.hudson-ci.org/docs/index.html [2] http://gradle.org/0.9.2/docs/userguide/userguide.pdf -- *Toni Menzel - http://www.okidokiteam.com*
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
