Calendar
Tag Cloud
#asterisk #asterisk #voip #voip aastra Active Directory AD ADAM Amanda asterisk Asterisk Blog call centre callrecording Catalyst Clustering DBIC DBIx-Class debian Digium Directory Services Disaster Recovery Dojo eDirectory Enterprise Backups Enterprise Directory Fedora Fedora Directory Server Fedora DS Flexi Time FreeSWITCH freeswitch Gnome IAM Identity Management IDM IP Telephony Isode Jabber/XMPP JavaScript Kamailio ldap LDAP LDAP Replication LDAP Schema linux Linux M-Vault Microsoft Microsoft FUD MirrorMode MySQL NBD OID on-hold OpenDS OpenLDAP openldap OpenLDAP Newsletter OpenLDAP Quick Tips OpenSIPS opensips open source Open Source Oracle Oracle Internet Directory PABX Perl pikatechnologies pikawarp PostgreSQL RDBMS Red Hat Replication Request Tracker RT Samba Sendmail sip SIP Squid SSO Sun Sun Microsystems SunOne suretec Suretec suretec telecom surevoip SureVoIP Symas Symas OpenLDAP Ubuntu UC UM Unified Communications voip VoIP X.500 XMPP yubico
Tuesday, May 12. 2009
Nagios Fork - response from the father of Nagios
We're sure you've already heard the news, it's now old news but below are the official thoughts of the father of Nagios:
As many of you know, a recent fork of Nagios has been announced, accompanied with a flurry of activity in both the community and press. An email thread titled “Nagios is dead! Long live Icinga!” began last week on the nagios-devel mailing list to kick this off.
What are my thoughts on this announcement? I think its one of the best things to ever happen to Nagios.
Why? The announcement of the fork, along with the community’s reaction to it has brought to light several things:
- Community interest in furthering Nagios is at an all-time high
- Community developers want to get more directly involved in the future project direction
- Nagios development has been slowed by some bottlenecks
- When the community perceives a problem, the community reacts
- Communication within the community needs to be improved
This entire event has seen some ugly misconceptions and half-truths lobbed in the direction of Nagios Enterprises, the Nagios Project, the Nagios Community, and myself as an individual. That’s unfortunate.
We think it's a good thing as it highlights problems which can clearly be solved if everyone agrees to work things out. If not, it's Open Source software so won't die. That's the beauty!
Suretec®
As many of you know, a recent fork of Nagios has been announced, accompanied with a flurry of activity in both the community and press. An email thread titled “Nagios is dead! Long live Icinga!” began last week on the nagios-devel mailing list to kick this off.
What are my thoughts on this announcement? I think its one of the best things to ever happen to Nagios.
Why? The announcement of the fork, along with the community’s reaction to it has brought to light several things:
- Community interest in furthering Nagios is at an all-time high
- Community developers want to get more directly involved in the future project direction
- Nagios development has been slowed by some bottlenecks
- When the community perceives a problem, the community reacts
- Communication within the community needs to be improved
This entire event has seen some ugly misconceptions and half-truths lobbed in the direction of Nagios Enterprises, the Nagios Project, the Nagios Community, and myself as an individual. That’s unfortunate.
We think it's a good thing as it highlights problems which can clearly be solved if everyone agrees to work things out. If not, it's Open Source software so won't die. That's the beauty!
Suretec®
Site Feeds
Quicksearch
Links
Categories
Powered by
Comments