Hi folks, I'm posting this to both general and chandler-users, but if you want to follow up please, let's keep it to a single list <[email protected]>, thanks.
Based on some previous discussions <GettingStartedGuideDiscussion20070628<http://chandlerproject.org/Journal/GettingStartedGuideDiscussion20070628>> I have begun creating a multi-chapter html document that is currently served from the chandlerproject wiki. There is a three-fold purpose: 1) a "Quickstart Guide" to walk new users through the process of getting Chandler up and running; 2) to provide the beginnings of a real, comprehensive user manual; and 3) to be a reference guide and source of documentation (e.g. screenshots and explanations) for the various features and functions of Chandler whose sections may be extracted, linked, and referenced by other documents. We should consider the current document a work-in-progress that will be enhanced right through the Chandler 1.0 release. But the short-term goal is to have something self-contained that a person can use to get started with the Preview Release of Chandler. I plan to have most of the chapters in at least a draft version by 8/13 since we are planning to test the Get Started Guide with new KEI users next week. If you have time to review the GsG < http://chandlerproject.org/pub/Product/GetStartedGuide/TableOfContents.html> and provide some feedback that would be great! If you find a error (commission or omission), or have specific suggestions on how to improve the content or presentation - file a bug in Bugzilla under product=OSAF, component=Get Started Guide < https://bugzilla.osafoundation.org/enter_bug.cgi?product=OSAF&component=Get%20Started%20Guide >. You can use the Priority field to let me know if I have to drop everything and fix it NOW because it is glaringly incorrect or something important is absent (P1). Or if it's OK, but could be better and we can wait until a couple weeks to fix it, give it a P3 or more. I'm going to use Bugzilla to manage the fixes/changes/additions to the GsG, so make those bugs very granular. If you want to have a more general discussion about the approach or process let's do it on the list. BTW, I am not using svn to manage version control, so if you go in and change one of the files, it's just going to get overwritten the next time I push my page to the server - no rollback, no merge, etc. So if you want to volunteer to do some hands-on work, please coordinate with me first. Thanks, Pieter [EMAIL PROTECTED]
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "General" mailing list http://lists.osafoundation.org/mailman/listinfo/general
