Ton Voon wrote: > I want to clarify some of the basic principles that we are adopting > with this strategy.
<snip> > So what is our proposed solution? We've turned the "less features" on > its head. > > Opsview Community actually will actually have **more** features than > Enterprise because it is bleeding edge. It will be the latest code, > with all the newest enhancements and performance tweaks. It will > contain all cumulative fixes. <more snip> > j.roberts says "Who exactly *wants* an *unstable* network monitoring > system? Who *wants* 'early and often' in their monitoring? Not me." > > Then I'd argue you are exactly the type of person that would benefit > from the Enterprise edition. > > If not, well, when a new release comes out, there's nothing stopping > you from *not* upgrading. So stick with your working system. But there's the crunch. That's what I'll probably do! It's what I do anyway, I have a constitutional allergy to 'bleeding-edge' on the infrastructure side. But surely you need people to use the new code to test the new features so that they can be debugged and rolled out into the 'Enterprise' version? So is this not likely to be somewhat counter-productive? > In summary, Opsera are open source advocates. We firmly believe in the > freedom of software: that when it exists on your servers, that you > have the freedom to make changes to it as you see fit. We think this > solution still gives those freedoms, while supporting continued > development in Opsview. Lest I appear to be negative in my comments, some thanks for Opsview is overdue. I enjoy it: it combines (as I have said) the stability of Nagios (which I trust) with a bow to non-command line people, and an improved set of standard capabilities (and some better monitors). So, Thank You! I support your need to find an income stream from your work: I'm just not convinced this is the way. But that's not my problem. A practical suggestion: Why not set up a facility to anonymously audit the configuration and scale of Opsview installations and (electively, opt-in) upload this information to you to load in a database somewhere so that you can see what facilities are being used, what monitors, how many systems, etc. etc.? I understand that some people may not like this idea, so you could restrict it to just the community edition. This could either be set to run on a scheduled basis (monthly?) or one-off, and be entirely elective so those working in tight regulatory environments would not need to worry about any leakage (but they would probably use the Enterprise vbersion). But I at any rate would be more than prepared to supply such information to you so that you can weight your efforts not only by feature demand or by sponsorship, but also by demonstrated utility and thus overall added-value? I would think that this might offer useful information that you could use to maximise your income potential by addressing work most profitably. Just an idea. -- James Roberts Stabilys.com _______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/listinfo/opsview-users
