Yes the requirements contained in this ticket are primarily geared
toward the "how". I think we believe that the how will provide an
infrastructure to support more rapid integration of content into a
system. Basically exponentially more, and better content through
better infrastructure. There is just a ton of content that is being
developed everyday, both here and in the community and we want to
make sure it is all usable, searchable and organized etc.
Thanks for the direction toward some of the more advanced tasks. That
is really where we are trying to improve for the next release. There
will likely be some form of an advanced/developers guide to support a
lot of this knowledge. And just think if you like Zenoss power at
50%, you haven't seen anything yet :-) We will do our best to get you
there with the docs.
On Feb 2, 2007, at 10:27 AM, Mohamed Hussein wrote:
It sounds to me like your requirements are more concerned about how
to write the doc and present it than the contents.
I feel that the current documentation is very lacking in terms of
doing "advanced" tasks.
I think more documentation for adding mibs and extending the RRD
templates would be very helpful.
Using zProperties to tune the system's behavior also can use better
documentation.
There is an obvious need for better documentation on automating
tasks.
Documenting the various independent scripts and maybe even the API
would be great.
I frankly feel that I am not using even 50% of zenoss power because
I can't find straight foward documentation and I am too busy to
keep digging in code.
Good luck
_______________________________________________
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
