Todd,
Thanks for the feedback. Basically another item that we would want to
have in a potential doc system is that it will be open, just as the
code is for development. For example, if there is a particular issue
that you (or any user) had or an area where you forged ahead despite
a lack of docs, we want to be a situation where you (a user) can
actually contribute to the doc set. In this way, we can add content
as a function of the improved doc development environment. I love the
idea of tagging too, like in a wiki so you could view all that are
tagged, and users can tag the information we create for even more
organization possibilities. There just don't seem to be great tools
for doing that now.
I love the idea of adding more in the docs about scripts and how they
interact. I think as the user community evolves into more advanced
users (as we are seeing ppl really do some great things) the doc
content will be evolving also to support that.
Thanks again for the feedback and we will be working hard to add more
content and make Zenoss even easier to use and extend.
Drew
On Feb 1, 2007, at 9:22 PM, Todd Davis wrote:
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
