> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, July 22, 2005 12:35 PM > To: Herb Martin > Cc: [email protected] > Subject: Re: PROPOSAL: create "SpamAssassin Rules Project" > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > greetings from CEAS! > > Herb Martin writes: > > Normally in an open source project anyone who wishes to > > listen, lurk, and read or even use the bleeding edge code > > is free to do so to learn and get into the frame of the > > project. > > > > That cannot be true (to the same extent) if there are > > security layers that make such gradual involvement > > difficult. > > Yep, this is entirely true -- and this is the reason why the > ASF suggests > that lists should be open if at all possible. > > It's a tricky conundrum -- need to think about this some more...
I don't see official rules majorly discussed in the open now. With a new release of SA, you don't go into detail about what new rules are looking for, so why should that change. People who update from SARE, just hear: "Hey xxxx.cf got updated." And they go and get it. Or they don't even know it gets updated and the RDJ script does it. So public is pretty good at just accepting the rule updates. Having an open public discussion on new rule ideas, pretty much defeats the purpose. I can honestly say that if that is how SA decides to do it, most SARE members would just continue to perfect the initial rule ideas on the private SARE list, and when 90% complete, move it over to the SA list for testing. No one wants their work made useless before it is even released. We have seen it before. --Chris
