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:Frost, Mark {PBG} (mark@pepsi.com)
Date:Feb 25, 2010 8:17:49 am
List:net.sourceforge.lists.nagios-devel

-----Original Message----- From: Marc Powell [mailto:ma@ena.com] Sent: Thursday, February 25, 2010 10:54 AM To: Nagios Developers List Subject: Re: [Nagios-devel] The nagios community wants to keep its open soul

As far as the future of Nagios, it is Ethan's project, not ours; it always has
been and >we are along for the ride. We can have hopes and dreams about what it
can become and >Ethan may buy into them, or he may not. We can propose
contributions and he may accept >them, or he may not. Regardless, we will all
make our own decisions about whether this is >compatible with our own goals.
Some will stay, some will move on. C'est la vie.

I agree with Marc. However, one thing that continues to puzzle me is what
exactly the core developers do. It was my understanding that when Ethan announced the addition of some core developers that there would be more changes to the core.
I thought that meant that those core developers could

- evolve the Nagios core on their own based on their own judgments, agreement of other core developers and perhaps input from the community as appropriate

- accept patches as appropriate from the community and implement them

It was not my understanding that Ethan would continue to be the sole person who touched the core and made all decisions about the core. That is that if Ethan doesn't do it, it doesn't get done. So I'm confused.

Now, I totally appreciate and admire what I've seen getting done in terms of
smaller patches and particularly the Merlin/Ninja work, but that's not really core work. I know that the work that people like Andreas do is funded by Op5 and I don't
have a problem with that. I don't quite know where the time and possibly money would
come from to develop the core, but I agree it does need to happen. I've seen many good messages from Andreas about things that need to be redone/reworked in the
core and have wondered how they ever will get done. It's probably more work than members of the community would take on themselves. Perhaps I would have hoped that Nagios Enterprises might fund the core team to make those changes but maybe that's my imagination.

So I'm still a very happy Nagios user and like the work I see happening, I'm
just wishing there'd be more.

-Mark

------------------------------------------------------------------------------ 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. http://p.sf.net/sfu/intel-sw-dev