I agree with Todd on this! But it does not do a very good job of describing advanced feature nor the many scripts available in the system.
If we had in the doc of all the scripts that can be run and what they do, it would most likely lead to less questions. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Todd Davis Sent: Thursday, February 01, 2007 9:23 PM To: 'General discussion of using zenoss system' Subject: RE: [zenoss-users] Question to Users about Zenoss Docs Personally for me, the format and presentation right now are secondary to content. What you've outlined sound good for the documentation system. Although this list provides a wealth of information, much of it doesn't seem to get rolled into the documentation (including the wiki). The admin guide provides pretty good guide for setting up Zenoss (with some gaps), but it does not do a very good job of describing advanced features nor the many scripts available in the system. The admin guide provides descriptions of all of the zProperties, but not necessarily how they need to be set in conjunction with each other to produce the desired functionality. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Drew Bray Sent: Thursday, February 01, 2007 3:56 PM To: [email protected] Subject: [zenoss-users] Question to Users about Zenoss Docs Hey all, We are going to try to revamp the format and presentation of the Zenoss doc set soon and would love some input. We have a few ideas of basic requirements but we definitely want some input from the community. What would you like to see? Here is what we have so far and we will be evolving these requirements as part of ticket #949 (http://dev.zenoss.org/trac/ ticket/949) Authoring environment needs to be * web publishing environment needs to allow users to make comments in the document. * easy to use * inexpensive (OSS preferred) * must support graphics * spell checking! * save documents in an open format * modular like wiki, but able to export and inport to more traditional formats for packaging - like .pdf * allow documentation to be integrated into contextual help within the zenoss application What do you think? What do you want to see? What would make it easier for you? Thanks, Drew Zenoss docs guy _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
