OpMon and Fruity, a better understanding.

[Taylor Dondich]

Hi all, might have seen a bit of an irate email from me regarding
OpMon and it's use of Fruity as it's initial codebase.  After
discussing it with the OpMon team, they had good reason to fork the
project.  They didn't really ping the user community mailing list or
myself in regards to forking the project, but they did submit patches.
 And because of the issue of Fruity being in a stale situation, their
patches could not go into the official codetree.

I've discussed with them how Fruity is basically no longer supported
and really should not be used for production use.  At least not with
Nagios 3.x  OpMon team did a good job of adding some initial support
for Nagios 3.x but there would be a lot of work to be done to try and
get the Fruity codebase up to par.  The good news is that I've already
done so and built Lilac, which is from the ground-up a major rewrite
of Fruity to support Nagios 3.x and be much more robust.

I'm now in discussions with the OpMon team in how we can leverage
Lilac for their uses and bring some of the work they've done to Lilac
and it's community.

Glad we got things cleared up the open source way!  By flaming and
communication.  8)

-- 
Taylor Dondich
Check out Lilac, a configuration tool for Nagios 3 at
http://www.lilacplatform.com

Check out my Shortcut with O'Reilly Press:
Network Monitoring with Nagios:
http://oreilly.com/catalog/9780596528195/index.html

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null