<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Hi L.B now I must also start giggling. It is really sad to see what happens at the moment or past months. Ethan only got business and dollars in mind, and start weeping out everything that could get in his way. He and Nagios Enterprise forgot that the community made Nagios such a success, and not his core software. Without all the patches,addons,plugins,support etc.. from the COMMUNITY, Nagios would never ever stand there where it is at the moment. His reaction on the posting on the list with his "nagios-drama list"(alias <code>>/dev/null 2>$1)</code> shows us what he think about his community.(waste people´s time) Maybe he don´t like the Community so much any more, because they give to much free support on other community sites, and he loses out with his Nagios Enterprise. They guys in France postet about Icinga, and he don´t liked it. Why not??? Maybe the community don´t like the way Ethan is going, and read about Icinga and see there are the community welcome, and so on ..., and think, hey, lets give it a go. Sure that he don´t like that, means he is going to lose out with his licenses fees. But my opinion is he is almost forcing the people to give other like Icinga,OP5,Groundwork etc.. a try. Really sad to see what is happening with Nagios!! It is no good publicity for him and Nagios. The first article is already out on a German site whit a Title "Nagios: gap between author and community deepens" Here are a google translate of the <a href="http://translate.google.de/translate?u=http%3A%2F%2Fwww.zdnet.de%2Fnews%2Fwirtschaft_unternehmen_business_nagios_kluft_zwischen_autor_und_community_vertieft_sich_story-39001020-41527909-1.htm&sl=de&tl=en&hl=&ie=UTF-8">artcile</a> Greetings Rudolf Am 27.02.2010 17:31, schrieb L B: <blockquote cite="mid:da03fe3e1002270831o6f9bb6b1k4343549375d57624@mail.gmail.com" type="cite"> <pre wrap="">Mark, The worst is that I'm sure it doesn't astonish anyone on the mailing list. Maybe you should consider sending your patch to nagios-drama, who knows... -- L.B. On Fri, Feb 26, 2010 at 11:38 PM, Gius, Mark <a class="moz-txt-link-rfc2396E" href="mailto:mgius@createspace.com"><mgius@createspace.com></a> wrote: </pre> <blockquote type="cite"> <blockquote type="cite"> <pre wrap="">-----Original Message----- From: Andreas Ericsson [<a class="moz-txt-link-freetext" href="mailto:ae@op5.se">mailto:ae@op5.se</a>] Sent: Friday, February 26, 2010 7:38 AM To: Nagios Developers List Subject: Re: [Nagios-devel] The nagios community wants to keep its open soul On Fri, Feb 26, 2010 at 4:00 PM, anthony paradis <a class="moz-txt-link-rfc2396E" href="mailto:funkyman78@hotmail.com"><funkyman78@hotmail.com></a> wrote: </pre> <blockquote type="cite"> <pre wrap=""> I expect a professional response from you </pre> </blockquote> <pre wrap=""> 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 : But alright, I'll come in with a professional response here. Most software projects expect the users who want features in the core code to develop those features themselves and submit patches that can be discussed and polished to perfection. The Nagios community works a bit differently. Users are crying out for new features, although they're often not very specific about what those features are supposed to be, and even more rarely users post patches to make that particular feature happen. 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. </pre> </blockquote> <pre wrap=""> A few months ago, I went through the process for A. In early November, I posted a query about an issue my company was having with service escalations and long-standing "warning" states. Gmane seems to be down right now, so I can't post a link to it, but original email sent to nagios-users 2009/11/05 at around 6:49PM PST, subject "Escalate after X warnings or critical." The feature I wanted didn't exist, so I downloaded the source and patched it in myself. On 2009/11/17, I posted a patch to nagios-devel, and updated it twice. Once at the request of Hendrik Baecker, and once to add my new configuration directives to the HTML docs. I have heard nothing about the possible inclusion or exclusion of this patch to the mainline tree since then, although I did specifically ask if there was a step I had missed that was preventing my patch from being considered. I understand that my patch was unsolicited, and may not be in the direction that Nagios wishes to go, but the complete lack of response was rather irksome to me (and is somewhat related the "Ethan doesn't listen" complaints that pop up from time to time). If the Nagios team had rejected my patch and given a reason (not in the right direction, no testing, breaks case foo, etc.), it would give me a direction to go in regards to eventually integrating my patch. As it stands now, I have to maintain my own private fork indefinitely because I simply don't know whether my patch is going to be accepted upstream. Just my experience here. Mark Gius </pre> </blockquote> <pre wrap=""> ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. <a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/intel-sw-dev">http://p.sf.net/sfu/intel-sw-dev</a> _______________________________________________ Nagios-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Nagios-devel@lists.sourceforge.net">Nagios-devel@lists.sourceforge.net</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/nagios-devel">https://lists.sourceforge.net/lists/listinfo/nagios-devel</a> </pre> </blockquote> </body> </html>