Re: [Nagios-devel] The nagios community wants to keep its open soul
Posted: Fri Feb 26, 2010 8:56 pm
--_ef1fc78f-5fc9-4887-94f1-d060e66fb4e7_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Andreas=2C=20
Thank you for your answer=2C
but i would like =20
=09
=09
=09
=09
=09
=09
=20
=20
a official and professional answer fr=
om nagios entreprise.
AP
> Date: Fri=2C 26 Feb 2010 16:37:49 +0100
> From: [email protected]
> To: [email protected]
> Subject: Re: [Nagios-devel] The nagios community wants to keep its open s=
oul
>=20
> On Fri=2C Feb 26=2C 2010 at 4:00 PM=2C anthony paradis wrote:
> >
> > I expect a professional response from you
> >
>=20
> Is it just me who can picture Ethan giggling away at the keyboard while
> he was writing that email? Personally=2C I thought it was hilarious
>=20
> But alright=2C I'll come in with a professional response here.
>=20
> 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=2C althoug=
h
> they're often not very specific about what those features are supposed
> to be=2C and even more rarely users post patches to make that particular
> feature happen.
>=20
> It's really quite simple. If you have a feature you want implemented=2C
> you can
> a) submit a patch to make it happen.
> b) whine.
>=20
> If you're a positive person (like me)=2C you'll try to make it happen fir=
st.
> If that fails=2C you can ask for help with a message like "hey=2C I tried=
this
> but can't make it work. Here's what I want to achieve and why I think
> that's a really stellar idea. Is anyone else capable of making this fly?"
>=20
> With that attitude=2C it's really a breeze to get exactly what you want
> from practically anybody. Demanding nameless features that you're
> not sure what they would do is a surefire way of getting no response
> what so ever.
>=20
> So let's have a look at what requests there are on Nagios. These are
> from ideas.nagios.org=2C which I assume is a decent collection of ideas
> that people share. I've only bothered with the top five or so=2C since it
> already shows a very very clear pattern without going further than
> that.
>=20
> * New gui. Lots of people want this. Well=2C that's something that can
> easily be implemented outside the nagios core=2C and there's currently
> at least two teams working on making that true. One is at op5 and
> the other is the icinga team.
>=20
> * Clustering/redundancy/loadbalancing/failover stuff. A lot of
> competent programmers (Nagios core devs included) all agree that
> such a feature needn't reside inside the Nagios core itself=2C but would
> be much better off written as a module. DNX=2C Merlin and other efforts
> are under way and are nearing production quality or are already on
> it.
>=20
> * New statusmap. Well=2C we at op5 have developed several already.
> They're free for grabs=2C since we've made sure to publish all our git
> repositories. You want to fly around in a 3d landscape in a java app?
> It's there for the taking. You want something that works with google
> maps and lets you draw whatever you want on a map? That too is
> already there=2C contributed back to NagVis=2C which we decided to use
> for that particular thing. You want something where hostgroups and
> their parent relations are drawn? lo and behold=2C we have that too.
> Download it and install it. If you can't figure out how to make it work=
=2C
> that's a different issue that we can work with after you've tried and
> failed.
>=20
> * Web frontend for configuration
> Nacoma (the op5 written tool) has been opensource and totally
> free for the past year or so. Go grab it. It works wonderfully for
> our 400+ customers and we actively develop it.
>=20
> * SLA reporting tool
> Again=2C it's up for grabs from the op5 git repositories. Just download
> and install it and you'll have corporate quality reports. Again=2C we do
> actively develop it.
>=20
>
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Andreas=2C=20
Thank you for your answer=2C
but i would like =20
=09
=09
=09
=09
=09
=09
=20
=20
a official and professional answer fr=
om nagios entreprise.
AP
> Date: Fri=2C 26 Feb 2010 16:37:49 +0100
> From: [email protected]
> To: [email protected]
> Subject: Re: [Nagios-devel] The nagios community wants to keep its open s=
oul
>=20
> On Fri=2C Feb 26=2C 2010 at 4:00 PM=2C anthony paradis wrote:
> >
> > I expect a professional response from you
> >
>=20
> Is it just me who can picture Ethan giggling away at the keyboard while
> he was writing that email? Personally=2C I thought it was hilarious
>=20
> But alright=2C I'll come in with a professional response here.
>=20
> 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=2C althoug=
h
> they're often not very specific about what those features are supposed
> to be=2C and even more rarely users post patches to make that particular
> feature happen.
>=20
> It's really quite simple. If you have a feature you want implemented=2C
> you can
> a) submit a patch to make it happen.
> b) whine.
>=20
> If you're a positive person (like me)=2C you'll try to make it happen fir=
st.
> If that fails=2C you can ask for help with a message like "hey=2C I tried=
this
> but can't make it work. Here's what I want to achieve and why I think
> that's a really stellar idea. Is anyone else capable of making this fly?"
>=20
> With that attitude=2C it's really a breeze to get exactly what you want
> from practically anybody. Demanding nameless features that you're
> not sure what they would do is a surefire way of getting no response
> what so ever.
>=20
> So let's have a look at what requests there are on Nagios. These are
> from ideas.nagios.org=2C which I assume is a decent collection of ideas
> that people share. I've only bothered with the top five or so=2C since it
> already shows a very very clear pattern without going further than
> that.
>=20
> * New gui. Lots of people want this. Well=2C that's something that can
> easily be implemented outside the nagios core=2C and there's currently
> at least two teams working on making that true. One is at op5 and
> the other is the icinga team.
>=20
> * Clustering/redundancy/loadbalancing/failover stuff. A lot of
> competent programmers (Nagios core devs included) all agree that
> such a feature needn't reside inside the Nagios core itself=2C but would
> be much better off written as a module. DNX=2C Merlin and other efforts
> are under way and are nearing production quality or are already on
> it.
>=20
> * New statusmap. Well=2C we at op5 have developed several already.
> They're free for grabs=2C since we've made sure to publish all our git
> repositories. You want to fly around in a 3d landscape in a java app?
> It's there for the taking. You want something that works with google
> maps and lets you draw whatever you want on a map? That too is
> already there=2C contributed back to NagVis=2C which we decided to use
> for that particular thing. You want something where hostgroups and
> their parent relations are drawn? lo and behold=2C we have that too.
> Download it and install it. If you can't figure out how to make it work=
=2C
> that's a different issue that we can work with after you've tried and
> failed.
>=20
> * Web frontend for configuration
> Nacoma (the op5 written tool) has been opensource and totally
> free for the past year or so. Go grab it. It works wonderfully for
> our 400+ customers and we actively develop it.
>=20
> * SLA reporting tool
> Again=2C it's up for grabs from the op5 git repositories. Just download
> and install it and you'll have corporate quality reports. Again=2C we do
> actively develop it.
>=20
>
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]