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 wrote:
>> -----Original Message-----
>> From: Andreas Ericsson [mailto:[email protected]]
>> 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
>> 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. =A0In early November,=
I posted a query about an issue my company was having with service escalat=
ions and long-standing "warning" states. =A0Gmane seems to be down right no=
w, so I can't post a link to it, but original email sent to nagios-users 20=
09/11/05 at around 6:49PM PST, subject "Escalate after X warnings or critic=
al." =A0The feature I wanted didn't exist, so I downloaded the source and p=
atched it in myself.
>
> On 2009/11/17, I posted a patch to nagios-devel, and updated it twice. =
=A0Once at the request of Hendrik Baecker, and once to add my new configura=
tion directives to the HTML docs. I have heard nothing about the possible i=
nclusion or exclusion of this patch to the mainline tree since then, althou=
gh I did specifically ask if there was a step I had missed that was prevent=
ing my patch from being considered.
>
> I understand that my patch was unsolicited, and may not be in the directi=
on that Nagios wishes to go, but the complete lack of response was rather i=
rksome to me (and is somewhat related the "Ethan doesn't listen" complaints=
that pop up from time to time). =A0If the Nagios team had rejected my patc=
h and given a reason (not in the right direction, no testing, breaks case f=
oo, etc.), it would give me a direction to go in regards to eventually inte=
grating my patch. =A0As it stands now, I have to maintain my own private fo=
rk indefinitely because I simply don't know whether my patch is going to be=
accepted upstream.
>
> Just my experience here.
>
> Mark Gius
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]