Nagios 2.0!

[Andreas Ericsson]

Tom DE BLENDE (GCC) wrote:
> 
> 
> Andreas Ericsson wrote:
> 
>> although I'm sure most people look at the level of the reply depth 
>> indicators (usually a '>' sign) and quickly deduce who wrote what.
> 
> 
> You want a screen capture of how it looks in Mozilla? I am familiar with 
> the concept of depth indicators.
> 

It's beside the point. I didn't post it. Some other user already 
acknowledged he did, so why not just drop it?

>> What's that got to do with anything?
> 
> 
> I'll explain it to you. You and your company make money out of Nagios. 
> So (quick) updates to (alpha) code are important to you, as you 
> obviously are using this alpha code in production environments. If code 
> changes are not applied in a timely fashion for you, your job becomes 
> harder, because what you deploy and what is in CVS gets out of synch.
> 
> The problem however, is that Ethan is not making any money out of 
> Nagios, and thus development isn't always as fast, changes don't get 
> applied at regular intervals. I'd say: learn to live with that. If you 
> CAN'T live with that, fork the project and do it yourself.

But then whatever I wrote won't be posted back to the community. Don't 
get me wrong, It's a fairly simple matter to fork the code and keep it 
up to date with CVS, but if I (or any other developer) do, we'll lose 
the very thing that has been the backbone of the open source community 
since Richard Stallman took his first steps toward a keyboard; User 
contribution.

> In my very 
> humble opinion, it is bad manner to put the amount of stress on Ethan to 
> commit changes and spend time on the project as you do.

I wasn't. I was trying to work around that by allowing other prominent 
contributors to gather up their patches someplace where they could be 
kept for later perusal by Ethan. That way we could all keep working and 
be sure that no two contributors work on the same bug/extension/whatever.

> Again: for you  it's a living,  for him it's a hobby.

Actually, I do most of my Nagios coding on my spare time.

> I would hate to see Ethan leave the 
> project because he gets too much pressure from the community, and 
> decides it is not worth it anymore...
> 

Me too. I would also hate to see a contributor walk away because the 
founding father doesn't respond (a simple yes or no would do) to posted 
code or well thought through suggestions. Nagios can survive without 
Ethan (although under a different name for legal reasons), but no 
opensource project can thrive without active contributors.

> Have a nice weekend...

Likewise.


On a side-note;
I do read the list. There's really no point in sending To: me and Cc: 
the list.

On a side-note 2;
I would love to see your comments on the other and more relevant part of 
the message I posted.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl