-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 hi bret,
> Amen. well, that, at least, makes two of us ;-) ... > Keeping the environment simpler and similar tasks done in a consistent > manner is really essential in a lot of business environments. 100% agreed. and re: "the environment", here we've stumbled on an achilles-heel of opensource projects. most are organized in project "silos" ... i.e., "we care deeply" about stuff in our silo. but as for "inter-silo-coordination", often -- not always -- the response is "don't care" or "do it yourself". sigh. <snip> > As for the "we just write the rules, it's up to you how you get them", personally, i think both projects should recognize the necessary synergies between them, and work to "make it work" -- TOGETHER. <snip> > It doesn't help that half the time the web page that > points to the rules doesn't get updated with the version info. well, amen to that! > It's like SARE saying, we want you to use the rules, but we won't make > it easy to keep them updated. add to that the "it makes sense for SA admins" (lame ... sorry chris) argument! > I do really understand the reason there isn't "one place" to go for sa > rules. It's community-supported. OK. > But when sa starts providing a way > to make your rules more accessible and easy to keep updated-- I don't > understand the avoidance. > > Yes, an official way to update rules. again to Chris' earlier point ... update & delivery, yes. a "good thing" to have multiple, separate *sources* cheers, richard - -- /"\ \ / ASCII Ribbon Campaign X against HTML email, vCards / \ & micro$oft attachments [GPG] OpenMacNews at gmail dot com fingerprint: 50C9 1C46 2F8F DE42 2EDB D460 95F7 DDBD 3671 08C6 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iEYEAREDAAYFAkTcto8ACgkQlffdvTZxCMYwPwCgwH/SYkaaJOrdwn62Nvij/JEL m88An0TsYkuvLSck+4Q7mU7vqPY2uCQv =XyIy -----END PGP SIGNATURE-----
