I'd agree that wiki is a good place for collaboration and the development of this place of documentation too. But I just want to make sure that we use the website to have some kind of high level information, and also somewhat detailed first steps to get people going, we could take as an example what is available for DAS :
High Level : http://incubator.apache.org/tuscany/das_index.html Java Overview : http://incubator.apache.org/tuscany/java_das_overview.html And then, what DAS has available in the Wiki : User Guide : http://wiki.apache.org/ws/Tuscany/TuscanyJava/DAS_Java_Overview/RDBDAS_Java_User_Guide - Luciano Resende On 10/11/06, Kevin Williams <[EMAIL PROTECTED]> wrote:
I think the wiki is the best place for development of this type of documentation. It is so easy to update that I hope it will "invite" others to participate. I also like Venkat's idea to snapshot content developed on the wiki to include in a milestone distribution. -- Kevin and I like Venkat's suggestion Rick wrote: > I don't see the need for the wiki step or harvesting. Also goes for pdf. > If a group needs to collaboratively work on a document and the wiki > provides them the best means for that and they want to harvest that to > html, I'm perfectly fine with it. But , don't see this as required > step, I'm perfectly fine working on the xml/html. > > Venkata Krishnan wrote: > >> Here is how I see this... >> >> - We just about create one version of the doco for which ever subject >> (be it >> about the distros or about the extensions...). This doco must be >> organized >> such that the initial sections start with some high level stuf and >> futher >> down talk about deep details. >> - We would then extract the high level info and put it on the website >> and >> link up to the entire doco as pdf (or anyother form) as "For more >> details >> see this....". We also package this doc with the distribution. >> - The Wiki is where we will collaboratively develop these docs. The >> content in the wiki must be harvested into the master doc that I was >> mentioning in the first point... >> >> I cannot think of anything else to avoid duplicating documentation. >> >> Thoughts? >> >> - Venkat >> >> >> On 10/11/06, Rick <[EMAIL PROTECTED]> wrote: >> >>> >>> I think there were still quite a few of us that saw value of doco >>> with in >>> the >>> distro itself. >>> If true, not sure how we can easily reuse the wiki work as we could >>> with >>> html. >>> >>> ant elder wrote: >>> > Where should we be doing documentation for the M2 release >>> function? I'd >>> > started doing Anakia xml for the Tuscany website, but the DAS guys >>> are >>> > using >>> > the wiki, does this matter, should we try to be consistent? I >>> think the >>> > website is a better place for this type of thing, but its probably >>> > easier to >>> > be using wiki. >>> > >>> > ...ant >>> > >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
