atom feed42 messages in net.sourceforge.lists.nagios-develRe: [Nagios-devel] The nagios communi...
FromSent OnAttachments
Olivier JANFeb 23, 2010 1:35 am 
Olivier JANFeb 23, 2010 1:47 am 
Christian DöblerFeb 23, 2010 2:56 am 
Michael FriedrichFeb 23, 2010 4:57 am 
napFeb 23, 2010 5:52 am 
napFeb 25, 2010 2:05 am 
Andreas EricssonFeb 25, 2010 5:23 am 
Marc PowellFeb 25, 2010 5:55 am 
napFeb 25, 2010 6:08 am 
Michael FriedrichFeb 25, 2010 6:23 am 
Martin MelinFeb 25, 2010 6:27 am 
napFeb 25, 2010 6:43 am 
Marc PowellFeb 25, 2010 7:53 am 
Frost, Mark {PBG}Feb 25, 2010 8:17 am 
Andreas EricssonFeb 25, 2010 8:25 am 
Andreas EricssonFeb 25, 2010 9:07 am 
L BFeb 25, 2010 2:08 pm 
Ciro IriarteFeb 26, 2010 5:24 am 
anthony paradisFeb 26, 2010 7:00 am 
sebFeb 26, 2010 7:06 am 
Romuald FRONTEAUFeb 26, 2010 7:34 am 
Andreas EricssonFeb 26, 2010 7:37 am 
napFeb 26, 2010 11:52 am 
Gerhard LausserFeb 26, 2010 12:29 pm 
anthony paradisFeb 26, 2010 12:56 pm 
Michael FriedrichFeb 26, 2010 1:01 pm 
Gius, MarkFeb 26, 2010 2:38 pm 
L BFeb 27, 2010 8:30 am 
Michael FriedrichFeb 27, 2010 9:30 am 
LappiesFeb 27, 2010 9:45 am 
Sasc...@gfkl.comMar 1, 2010 7:19 am 
Andreas EricssonMar 1, 2010 7:58 am 
Andreas EricssonMar 1, 2010 8:05 am 
Andreas EricssonMar 1, 2010 8:32 am 
Michael FriedrichMar 1, 2010 9:08 am 
Ethan GalstadMar 1, 2010 9:00 pm 
Ethan GalstadMar 1, 2010 9:11 pm 
Andreas EricssonMar 1, 2010 11:15 pm 
Andreas EricssonMar 2, 2010 6:10 am 
Ethan GalstadMar 2, 2010 9:29 am 
Romuald FRONTEAUMar 2, 2010 9:50 am 
Gerhard LausserMar 2, 2010 10:25 am 
Subject:Re: [Nagios-devel] The nagios community wants to keep its open soul
From:Lappies (lapp@gmx.de)
Date:Feb 27, 2010 9:45:32 am
List:net.sourceforge.lists.nagios-devel

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 |>/dev/null 2>$1)| 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 artcile <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>

Greetings Rudolf

Am 27.02.2010 17:31, schrieb L B:

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<mgi@createspace.com> wrote:

-----Original Message----- From: Andreas Ericsson [mailto:ae@op5.se] 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 <funk@hotmail.com> wrote:

I expect a professional response from you

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.

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.

------------------------------------------------------------------------------ Download Intel&#174; 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. http://p.sf.net/sfu/intel-sw-dev

------------------------------------------------------------------------------ Download Intel&#174; 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. http://p.sf.net/sfu/intel-sw-dev