<tt>Hi Andreas,</tt> <tt>> Is it just me who can picture Ethan giggling away at the keyboard while > he was writing that email? Personally, I thought it was hilarious :D </tt> <tt>yes it was - but honestly I don't think it was the best choice in</tt> <tt>that particular situation. It was funny, but polemic.</tt> <tt> > It's really quite simple. If you have a feature you want implemented, > you can > a) submit a patch to make it happen. > b) whine. > > If you're a positive person (like me), you'll try to make it happen first. > If that fails, you can ask for help with a message like "hey, I tried this > but can't make it work. Here's what I want to achieve and why I think > that's a really stellar idea. Is anyone else capable of making this fly?" > > With that attitude, it's really a breeze to get exactly what you want > from practically anybody. Demanding nameless features that you're > not sure what they would do is a surefire way of getting no response > what so ever. </tt> <tt>Well, I sincerely doubt it really works that way.</tt> <tt>I'm using Nagios now for like 8 or 9 years or so.</tt> <tt>I have seen many ideas coming in over the last 2 years, I've seen</tt> <tt>many patches from eager Nagios contributors coming in the last 2 years,</tt> <tt>yet I still have to see that eager participation of the president of</tt> <tt>Nagios Enterprise (c)(r)[tm]. As already mentioned before, it's not</tt> <tt>actually the fact that not everything gets done in an instant, it's</tt> <tt>the fact that the president of Nagios Enterprises (c)(r)[tm] does</tt> <tt>not seem to care about what community members think or whatnot.</tt> <tt>There was no "nice patch, I'll get it in once I get the time" or</tt> <tt>"I'm unsure how the patch behaves, please provide me with a test</tt> <tt>scenario" or maybe even just a "your patch sucks, go away".</tt> <tt>It rather feels like a lot of people are discussing here to no</tt> <tt>avail - since the president of Nagios Enterprises (c)(r)[tm]</tt> <tt>is busy with business.</tt> <tt> > So let's have a look at what requests there are on Nagios. These are > from ideas.nagios.org, which I assume is a decent collection of ideas > that people share. I've only bothered with the top five or so, since it > already shows a very very clear pattern without going further than > that. > * New gui. Lots of people want this. Well, that's something that can [...] > * Clustering/redundancy/loadbalancing/failover stuff. A lot of [...]</tt> <tt>> * New statusmap. Well, we at op5 have developed several already. [...]</tt> <tt>> * Web frontend for configuration [...]</tt> <tt>> * SLA reporting tool </tt> <tt>Nice - but what about a bugfree core?</tt> <tt>Most complaints or wishes I have seen ignored here are actually only</tt> <tt>relevant to the core. All others, especially those mentioned above,</tt> <tt>are healthy open source projects that react quite quickly to requests,</tt> <tt>patches or questions. Let's take NagVis for example - I've contributed</tt> <tt>quite some ideas and even a few patches to the project and so far all</tt> <tt>of them have been either accepted, commented, denied or delayed for</tt> <tt>a future major release by a core dev within a few days.</tt> <tt>Ontop of all that is the fact that the president of Nagios</tt> <tt>Enterprises (c)(r)[tm] seems to be more busy with prosecuting</tt> <tt>websites that make "unofficial" use of the term Nagios (c)(r)[tm]</tt> <tt>in a manner that does not fit the president of Nagios</tt> <tt>Enterprises (c)(r)[tm]. That's really a shame and the reason is simple:</tt> <tt>All those websites and their users out there made Nagios the best</tt> <tt>free monitoring tool out there - because they dedicated their time</tt> <tt>for finding bugs, writing pathes, free tools, plugins, add-ons and</tt> <tt>whatnot. In my humble opinion it was those users that made Nagios a</tt> <tt>success - and not that little buggy thing called core. And now</tt> <tt>all those people get is a laugh in their face.</tt> <tt>We all hoped for changing times, when Ethan went inactive.</tt> <tt>Now we do have those changes big time - but I frankly doubt that</tt> <tt>anyone but Ethan is happy with them. You might go on with "Nagios</tt> <tt>is Ethans baby and he can do what he wants" - yes it is. But</tt> <tt>hundreds and thousands of codelines have been supplied by</tt> <tt>contributors in good faith and those get the shaft now.</tt> <tt>It's just sad to see what happened to a once prospering open source</tt> <tt>project. In my humble opinion Nagios is not what I consider an open</tt> <tt>source project anymore. It's someone's baby who now tries to</tt> <tt>aggressively cash cow it. It more and more looks like Ethan tries</tt> <tt>to beauty up the bride to sell out the name asap. I might be wrong,</tt> <tt>but my gut feeling and the current incidents make it look like that.</tt> <tt>Somehow this reminds me of the Mambo/Joomla drama, where a community</tt> <tt>got split because of someone agressively prosecuting his trademark</tt> <tt>on mambo and Joomla was born. Oh btw - anyone seen mambo in the</tt> <tt>news lately? Me not, Joomla has taken over it's place... come to</tt> <tt>think of it.</tt> <tt>I didn't provide any patches to nagios back then because</tt> <tt>Ethan ignored everything anyway and I considered them a waste</tt> <tt>of time. Now I'm really happy I didn't do it and I certainly</tt> <tt>won't provide any in the future...</tt> <tt>Regards</tt> <tt> Sascha</tt> GFKL Financial Services AG Vorstand: Jürgen Baltes Vorsitzender des Aufsichtsrats: Wilhelm Plumpe Sitz: Limbecker Platz 1, 45127 Essen, Amtsgericht Essen, HRB 13522