|Gerhard Lausser||May 6, 2009 2:58 am|
|Christoph Maser||May 6, 2009 3:54 am|
|Andreas Ericsson||May 6, 2009 4:13 am|
|Alexander Wirt||May 6, 2009 5:53 am|
|Hendrik Baecker||May 6, 2009 5:58 am|
|Andreas Ericsson||May 6, 2009 7:12 am|
|Andreas Ericsson||May 6, 2009 7:48 am|
|Ethan Galstad||May 6, 2009 8:55 am|
|Steven D. Morrey||May 6, 2009 9:27 am|
|Haydn solomon||May 6, 2009 11:21 am|
|Mathieu Gagné||May 6, 2009 11:33 am|
|Matthias Flacke||May 6, 2009 11:56 am|
|Steven D. Morrey||May 6, 2009 12:25 pm|
|Jeremy Hanmer||May 6, 2009 12:59 pm|
|Andreas Ericsson||May 6, 2009 1:47 pm|
|D. Emmanuel Feinsmith||May 6, 2009 2:15 pm|
|Steven D. Morrey||May 6, 2009 2:48 pm|
|Andreas Ericsson||May 6, 2009 3:42 pm|
|Matthias Flacke||May 6, 2009 3:45 pm|
|sean finney||May 7, 2009 12:22 am|
|Albrecht Dre?||May 7, 2009 2:15 am|
|matthias eble||May 7, 2009 2:19 am|
|Andreas Ericsson||May 7, 2009 2:22 am|
|Andreas Ericsson||May 7, 2009 4:32 am|
|Andreas Ericsson||May 7, 2009 7:07 am|
|Ingo Lantschner||May 7, 2009 7:57 am|
|Hendrik Baecker||May 7, 2009 9:52 am|
|Hendrik Baecker||May 7, 2009 10:31 am|
|Mathieu Gagné||May 7, 2009 12:21 pm|
|Bernd Erk||May 7, 2009 12:23 pm|
|Andreas Ericsson||May 8, 2009 12:19 am|
|Andreas Ericsson||May 8, 2009 12:30 am|
|Andreas Ericsson||May 8, 2009 12:42 am|
|Julian Hein||May 10, 2009 12:50 pm|
|Mark...@teliasonera.com||May 26, 2009 1:48 am|
|Andreas Ericsson||May 26, 2009 3:21 am|
|Mark...@teliasonera.com||May 26, 2009 3:44 am|
|Subject:||Re: [Nagios-devel] Nagios is dead! Long live Icinga!|
|From:||Hendrik Baecker (andu...@process-zero.de)|
|Date:||May 6, 2009 5:58:23 am|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Andreas Ericsson schrieb:
As a software engineer, I like what I see. As a friend of Ethan's and a longtime Nagios community member, this is just sad.
Even if I'm one of those mystique Icinga guys, I agree with you. It was a hard decision to do, what we are doing. It's not to commit an outrage to Ethan - just an very encouraged try to bring some active development back to a great monitoring tool.
The way I see it though, it's not too late to salvage this yet, but it would require quite a lot of work on Ethan's part, and a lot of goodwill from the newly founded Icinga team.
IMO, if Ethan would be more open to other contributors, a fork wouldn't be necessary. But there were so many tries to lead him helping hands. He never gives back a direct "No" or s.th. similar - but also he never took those hands.
Nagios' problem is, as stated, that Ethan is both inactive and the single bottleneck for all new patches and functionality that the community wants to include into the core one way or another. A solution to this would ofcourse be to be more free with handing out commit access and making the Nagios project more of a team effort. Ethan doesn't scale, but the community does.
This is one big goal for icinga. We want to be scalable instead of a single point of waiting / frustrating.
I hope Ethan wakes up and starts working with the community again, and that he does so because it's fun.
I'm not angry with Ethan, but I see Nagios to be dying if it goes forward in the same manner.
I hope Ethan moves to a DSCM and provides push access to prominent contributors in the community.
I think git should be good for this? I hope so, I realy don't want to loose all my commits on icinga.
I hope Icinga forks from that DSCM, and uses the same DSCM to maintain their own code so that a future merge becomes as painless as possible. Icinga forked from a cvs2git copy, so future merging might be possible.
I hope Icinga releases their code early, so they don't fall into the pitfall of keeping things in the dark, promising "any day now we'll have something that's technically superior to what Nagios has". I searched their site but found no source there now, so presumably they have nothing to show yet. This makes the programmer in me go "ouch, do they suck that much?"
I know what you mean. I feel very sorry that the current code is not accessible to the public right to the announcement day. It's a single fact, that the first code publishing will be just a renamed nagios, a "update-check-as-opt-in", a new 'configure', design and a included ndoutils/idoutils code. the actual code base is not compileable but it will be much nicer within the next days. I would hate the thought to publish non workable 'dirty' code.
I hope this isn't just a political stunt to get Ethan to come out of hiding. If it is, it's very bad form. Put up the code and I'll have no doubts this is genuine anymore ;-)
As I mentioned before. Code base will be opened in the next days as a pre-alpha, mega-super-testing phase ;) No, it's not only a political stunt to get Ethan to wake up again.
I hope Icinga keeps their promises of staying 100% nagios- compatible. op5 doesn't want to fork upstream projects, but we may have to to keep API's and whatnot stable.
We defined the nagios core components, like scheduling, alerting, and so on as good enough to kept untouched. So object and api handling should be fully compatible to nagios. The next steps should be a open development of the blocking ndoutils and better db abstraction. Of course we want to catch up the latest nagios related patches, test them and apply them upstream - a thing we are all missing for the moment, don't we?
Regards, Hendrik -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32)
iD8DBQFKAYmGlI0PwfxLQjkRAtKiAJ9+SQAnp0ziDcuUeM+Jwt9gDveWYQCeOiBw xbYEHVwyF1gRgRkcVsO3gjQ= =U8n4 -----END PGP SIGNATURE-----
------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________ Nagios-devel mailing list Nagi...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-devel