Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Organization: SipXecs Forum In-Reply-To: <camgknjuuppmrzst5yu43ka1npzh_dw2z_usj4fpm4mjdfgk...@mail.gmail.com> X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <66159> Message-ID: <[email protected]>
Tony Graziano wrote on Fri, 17 February 2012 02:30 > I think that bringing up Zenoss is a bad example. The > code and > documentaqtion is openly available for sipXecs. > Documentation and User > Manuals are two different things. > > BTW -- Zenoss is based on Zope. Zope is cool and a neat > way to handle > network monitoring, but isn't zope full of security > holes too? I think > it's funny. laugh. I'm referring to the user and implementation documentation, not code or code documentation. Zenoss keeps their installation and administration guides up to date and available to the community. I understand the reasoning for eZuce to keep their guides/manuals commercial-only, but was just suggesting that without commercial backing the community documentation/manuals/guides will likely not be up to date. Are you suggesting that Zenoss and Zope are the same thing? Zenoss (a monitoring solution) uses Zope (a web application server) for its web interface. I don't see any relevance to the documentation example I was giving, especially the comment about Zope security. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
