[Logcheck-devel] helping out on logcheck

[Zak B. Elep]

On Sun, 2009-09-13 at 11:18 +0200, martin f krafft wrote: 
> Depends on the level of involvement, nature of what you want to do,
> and available time:
> 
>   - bug triaging, committing patches, writing and committing filters
>   - preparing new releases
>   - working on bugs related to the logcheck script itself
>   - implementing macros, e.g. so that rules files are pre-processed
>     and I can use @IPV4_ADDRESS@ in place of the dozens of different
>     regexps floating around, which are used to match IPv4 addresses.

Sounds good.  I've just subscribed to the list, let me see what I can
do :)

> Let me know your alioth username so I can give you write access to
> the (Git) repo.

Cool, I'm zakame-guest at Alioth.  Looking forward to contributing!

-- 
Zak B. Elep -- 1486 7957 454D E529 E4F1  F75E 5787 B1FD FA53 851D
  I like the idea of 256 bits, though: 32 for the (Unicode) character
leaves room for 224 Bucky bits, which ought to be enough for anyone.
                        -- Roland Hutchinson, in alt.folklore.computers

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/logcheck-devel/attachments/20090914/d452e8f1/attachment.pgp>