Re: Is the logwatch project dying?

Stefan wrote:
> Hello list,
>
> I'm wondering if the logwatch project is slowly dying? Maybe the word 'dying' 
> is to harsh, but for me it seams at least that the maintainers doesn't care 
> much about the contributions which are made by outsiders (volunteers). We have 
> seen some messages to the list in which people ask about what happens with 
> send in patches. It's the same for me. I send in a couple of patches, nothing 
> happens. Then I resend the patches and I received at least a confirmation. But 
> that's all. No commit to CVS or a reply which tells me what's wrong with them.
>
> I'm not a experienced perl programmer but I can write patches to existing 
> scripts and I also can write new ones. And I would love to contribute my work, 
> but how can I if it takes more than half year until patches are accepted (or 
> rejected)?
>
> Now my questions: What is the status of the logwatch project? And is work from 
> outsiders still welcome?
>
> Finally, let me apologize for my forthright words.
>   

No apologies needed it's a totally fair question. As far as I know I am 
the only one doing any CVS commits. It has been this way for awhile. I 
wish I had more time and energy to get all the patches in and all that 
but the truth is I don't. Every 6 months or so I'll get fired up and try 
to catch up with the patches, I have them all tagged in my mailbox and 
all that but at the end of the day I'm one guy who has lots of other 
things I have to do.

How do we fix this? No idea I guess we need new blood. As far as how to 
get involved well the same way I did back in 2004 start patching against 
CVS and make it easy to get your patch in. The biggest slow down I have 
in committing is that patches are not against the CVS tree so I have to 
go in and figure out where is goes by hand. Then I have to make sure it 
does not break anything else, remember Logwatch basically works across a 
wide section of Linux, Solaris, and *BSD installs [heck I can get it to 
run under IRIX] so we want to make sure your patch is cross platform safe.

-Mike